Summary | Conflict Management |
Queue | Kronolith |
Queue Version | 2.1.2 |
Type | Enhancement |
State | Rejected |
Priority | 1. Low |
Owners | |
Requester | webmgr (at) muskingum (dot) edu |
Created | 08/17/2006 (6846 days ago) |
Due | |
Updated | 08/17/2006 (6846 days ago) |
Assigned | |
Resolved | 08/17/2006 (6846 days ago) |
Milestone | |
Patch | No |
the other ticket. Continuing to update this one isn't really helping.
things. In most cases, they say they are accustomed to checking
freebusy or looking at the calendar directly. The situation they
experience happens something like this:
The owner of the calendar is adding an event to his calendar, and
meanwhile his secretary is on the phone with someone else asking to
schedule the same time. On of them beats the other to the punch, and
one of them submits a short time later... now there's a conflict.
In the process, they both checked their availability (calendars are
side-by-side in Horde), saw nothing was scheduled, and proceeded
believing all was fine.
For that reason, primarily, they really prefer it if saving the event
resulted in a quick check and a prompt if it conflicted with another
appointment. From the prompt they could choose accept or decline...
accepting would create as it does now, decline would take them back to
the edit event page and allow them to pick a new time.
Any thoughts? I'm very willing to consider alternative ideas if you have any.
asked me about it and see what they think. I'll post again this
afternoon.
Not trying to be difficult, I just want to make things easy for users.
scheduling meetings with others... but what happens when it's your own
calendar and you forget that you have an appointment because you
(conveniently) "forget" to actually go to the day and visually confirm
you're free?
I was disturbed at the number of secretaries who "memorize" their
staff's schedules and encounter this problem. Clearly, I'm working to
try to retrain them to do it right, but sometimes these little things
have big benefits.
State ⇒ Rejected
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Conflict Management
Queue ⇒ Kronolith
State ⇒ New
management for new events.
Ideally, they would like to have options to either allow conflicts,
disallow them, or prompt if a conflict and give them the choice to
back out of the new event.