994205 - [meta] UX issues on changing calendar in event dialog

Status: NEW

(Calendar :: Dialogs, defect)

Description

[[:MakeMyDay]]

While investigating on bug 994200, I have observed some other issues, which should considered related to changing the calendar in event dialog maybe:

1) changing the calendar from one (e-mail) schedulding calendar to another
   (due to bug 994200 currently only reproducable with a target calDAV
   calendar)
   => user might not be aware, that this is in fact an event cancellation
      and a new invitation (at least until the OL comp dialog pops up)
   => OL compatibility dialog appears 2 times (1x for the cancellation, 1x
      new invitation)
   => if the new organizer (organizerId of the target calendar) was already
      an attendee, this results and shows up as a duplicate in the attendee
      dialog (1x organizer, 1 attendee). Is here something needed
      immidiately? In long term, this will be resolved with a changed
      concept for organizer handling as discussed in bug 459683.

2) changing from a non-scheduling calendar to a scheduling calendar
   => notify attendee box is available but not checked (though there are
      pros & cons to check it in this case by default - if not checked by
      default in case of calendar switch, a message in the notification
      bar would be probably nice. Otherway, the user might think his 
      invitation was sent out not noticing that the OL-popup did NOT appear 
      when pressing save & close)
   => user may not be aware that this is in fact an event invitation, if 
      still attendees exist

3) changing from a scheduling calendar to a non-scheduling calendar
   => user may not be aware that this is in fact an event cancellation
   => the notify attendee checkbox is greyed out, the invite attendee button
      isn't (shouldn't this be in sync?) and maybe related:
   => attendees (and organizer) are kept (this is probably more a feuture 
      than a bug, though)

As these are UX only issues and no real errors, do you think we should address one or more of the above?

Comment 1

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

(In reply to MakeMyDay from comment #0)
> 1) changing the calendar from one (e-mail) schedulding calendar to another
>    (due to bug 994200 currently only reproducable with a target calDAV
>    calendar)
>    => user might not be aware, that this is in fact an event cancellation
>       and a new invitation (at least until the OL comp dialog pops up)
Yes, this would be nice to have. The explanation might get too long, but ideally we can use the notification bar for this.

>    => OL compatibility dialog appears 2 times (1x for the cancellation, 1x
>       new invitation)
Given our current architecture, this might be hard to figure out. Before investing too much time here, I'd suggest revisiting if we need the OL compat dialog at all, now that some Outlook products are EOL'd. Possibly also something changed in the Thunderbird compose code that will allow us to determine the order of mime parts better.

>    => if the new organizer (organizerId of the target calendar) was already
>       an attendee, this results and shows up as a duplicate in the attendee
>       dialog (1x organizer, 1 attendee). Is here something needed
>       immidiately? In long term, this will be resolved with a changed
>       concept for organizer handling as discussed in bug 459683.
I think the long term solution is sufficient, no one has noticed this in the past afaik :)

> 
> 2) changing from a non-scheduling calendar to a scheduling calendar
>    => notify attendee box is available but not checked (though there are
>       pros & cons to check it in this case by default - if not checked by
>       default in case of calendar switch, a message in the notification
>       bar would be probably nice. Otherway, the user might think his 
>       invitation was sent out not noticing that the OL-popup did NOT appear 
>       when pressing save & close)
>    => user may not be aware that this is in fact an event invitation, if 
>       still attendees exist
So a fix for this would be to check the box when switching in this direction? If there are no downsides to this I wouldn't object.


> 
> 3) changing from a scheduling calendar to a non-scheduling calendar
>    => user may not be aware that this is in fact an event cancellation
The notificationbar solution mentioned above should inform the user of this

>    => the notify attendee checkbox is greyed out, the invite attendee button
>       isn't (shouldn't this be in sync?) and maybe related:
>    => attendees (and organizer) are kept (this is probably more a feuture 
>       than a bug, though)
I think it should be possible to maintain attendees without notifying them.

> 
> As these are UX only issues and no real errors, do you think we should
> address one or more of the above?
It doesn't hurt to address them as mentioned above. I'd suggest turning this into a meta bug and handling specific issues as dependencies.

Comment 2

[[:MakeMyDay]]

Turning this into a meta bug. I will follow up filing the separate bugs as appropriate.