After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 566525 - When receiving a meeting status update from an email address not listed for that meeting, the "add sender" dialog has only an "OK" button
When receiving a meeting status update from an email address not listed for t...
Status: RESOLVED DUPLICATE of bug 478090
Product: evolution
Classification: Applications
Component: Calendar
2.24.x (obsolete)
Other All
: Normal major
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-01-04 16:56 UTC by Oded Arbel
Modified: 2010-12-02 13:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Attachments
Screencast showing the problem (47.51 KB, image/png)
2009-01-04 16:56 UTC, Oded Arbel
Details

Description Oded Arbel 2009-01-04 16:56:23 UTC
Please describe the problem:
This is a serious usability problem - the calendar application asks a yes/no question: "Add the sender as an attendee?", but the dialog only offers an "OK" button where it clearly should have either OK/Cancel or Yes/No.

Steps to reproduce:
1. Send a meeting invitation to an alias of your primary mail account
2. when the meeting invitation is received, approve it using your primary mail address
3. when the approval arrives, click "update"


Actual results:
A dialog appears with a single OK button and no way to cancel the "add sender" action

Expected results:
The dialog that appears should have the option of canceling the add sender action

Does this happen every time?
yes

Other information:
A screenshot will be attached shortly
Comment 1 Oded Arbel 2009-01-04 16:56:56 UTC
Created attachment 125738 [details]
Screencast showing the problem
Comment 2 Milan Crha 2010-12-02 13:39:15 UTC
Thanks for a bug report. This is got fixed within bug #478090, thus I'm marking this as a duplicate of it.

*** This bug has been marked as a duplicate of bug 478090 ***