Summary | attendance.php should have an address book icon and auto expansion |
Queue | Kronolith |
Queue Version | HEAD |
Type | Enhancement |
State | Resolved |
Priority | 2. Medium |
Owners | chuck (at) horde (dot) org |
Requester | kevin_myer (at) iu13 (dot) org |
Created | 03/28/2005 (7401 days ago) |
Due | |
Updated | 01/29/2007 (6729 days ago) |
Assigned | 04/08/2005 (7390 days ago) |
Resolved | 01/29/2007 (6729 days ago) |
Milestone | 2.1 |
Patch | No |
State ⇒ Resolved
Taken from
State ⇒ Accepted
http://horde.org/bounties/details.php#kronolith_attendee_autoexpand
watched a user try to add multiple attendees and she expected the
field where addresses were entered to behave like IMP's address
expansion and addition capabilities.
Issue 1: If using the address book to look up entries, after all the
entries have been selected, those entries should go directly to the
attendees screen. A user should not have to select addresses, submit
to populate another form field, and then submit that field to populate
attendees.
Issue 2: Tab auto-expansion, an Address Book icon, and an Expand
Names icon provides a familiar environment for a user to find addresses.
Issue 3: The "Dismiss" button is unintuitively named. Dismiss almost
has a connotation of Cancel. A better setup would be to have a Cancel
button and a Save Attendees button.
State ⇒ Assigned
Priority ⇒ 2. Medium
Version ⇒ HEAD
address expansion options available in IMP (auto-expand, expand names,
etc.).
Then you start to introduce a consistency across all your
applications. They all start to behave the same way. When you get to
a screen where you want to pick people, you know that if you Tab,
you'll autoexpand for addresses (with the same caveat that you have to
pick a unique enough portion of the name to get a single result).
When you see an address book icon, you know you can do at will
searches. When there are consistent ways of doing things, users tend
to pick up on how to do things, better.
button to click.
We're still hitting issues with using this screen, because people are
assuming that it works kid of like the Mail composition screen - enter
a name or a part of a name and you'll end up with the full name and
address (which incidentally, would not be a bad feature to add :)
State ⇒ Resolved
addressbook button looked a little lost with your original patch. If
this causes the same confusion, I'd recommend an icon for the address
book like IMP has, instead of a button - that should help
differentiate them.
Priority ⇒ 1. Low
State ⇒ New
New Attachment: kronolith-attendees.patch
Queue ⇒ Kronolith
Summary ⇒ Useability enhancement for attendance.php screen
Type ⇒ Enhancement
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.