| Summary | Unavailable resources should do more than just show a message |
| Queue | Kronolith |
| Queue Version | Git master |
| Type | Enhancement |
| State | Resolved |
| Priority | 2. Medium |
| Owners | |
| Requester | horde (at) stefanseidel (dot) info |
| Created | 11/25/2013 (4261 days ago) |
| Due | |
| Updated | 01/23/2014 (4202 days ago) |
| Assigned | |
| Resolved | 01/23/2014 (4202 days ago) |
| Milestone | |
| Patch | No |
State ⇒ Resolved
cancelled, so it's much more visible to the user that there's
something wrong.
that if sending invites to other attendees, they will receive an
invitation to a cancelled event.
would leave "invalid" events in the calendar) or to prevent saving
the event unless all resources are available (might be too strict).
implement required vs optional resources if we do something like this.
Still, I don't see this as a big issue since the freebusy info of the
resource is available when adding it, so the likelyhood of a rejected
resource is low.
Priority ⇒ 2. Medium
Patch ⇒ No
Milestone ⇒
Queue ⇒ Kronolith
Summary ⇒ Unavailable resources should do more than just show a message
Type ⇒ Enhancement
State ⇒ New
are not available for that event, the only effects are:
- message is shown to the user, which can be easily overlooked
- no resource calendar event is created
IMO resources that are unavailable should somehow block the event.
Changing Event.php around line 575 from
" elseif($haveLock) {"
to
" else {
$this->status = Kronolith::STATUS_CANCELLED;
if ($haveLock) {"
will provide an initial solution: the event status is set to
cancelled, so it's much more visible to the user that there's
something wrong.
Another idea would be to show the message as an alert box (still it
would leave "invalid" events in the calendar) or to prevent saving the
event unless all resources are available (might be too strict).