[Tickets #1635] NEW: Useability enhancement for attendance.php screen

bugs at bugs.horde.org bugs at bugs.horde.org
Mon Mar 28 15:07:10 PST 2005


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=1635
-----------------------------------------------------------------------
 Ticket             | 1635
 Created By         | kevin_myer at iu13.org
 Summary            | Useability enhancement for attendance.php screen
 Queue              | Kronolith
 Version            | 2.0.2
 State              | New
 Priority           | 1. Low
 Type               | Enhancement
 Owners             | 
+New Attachment     | kronolith-attendees.patch
-----------------------------------------------------------------------


kevin_myer at iu13.org (2005-03-28 15:07) wrote:

During some beta testing and training modules development for a Horde
rollout, there was some confusion about how to properly add attendees for
checking availability.  What we discovered was that users were assuming that
the "Add people from my addressbook" would expand whatever was typed in the
"Add attendees" field.  So they'd type a first name, click on the button,
and not finding the entry there, do a search.  They'd find their desired
user and add them, but the "Add attendees" field also contained their
previous shortened name that they had typed.    Then when they clicked the
"Add these people" button, the real user and a bogus user would be added.

What this patch does is simple.  It attempts to introduce some segregation
between the "Add attendees" field, where users must be entered exactly, and
the "Add people from my Address Book".  In the logical order of things, you
would likely first add people from an addressbook, then include any manual
additions, then add the list to the overall attendees list.  It should help
reduce confusion between what the two "Add" buttons do.  One invokes the
addressbook, the other invokes adding attendees to the list up top.  Putting
them side-by-side caused confusion with our users.  Visually separating them
helped our users understand how to add attendees.




More information about the bugs mailing list