Skip to content
This repository has been archived by the owner on Dec 20, 2017. It is now read-only.

update designs for call to action on autofills when advisor needs new object #467

Closed
erincd opened this issue Mar 6, 2017 · 2 comments
Closed

Comments

@erincd
Copy link
Contributor

erincd commented Mar 6, 2017

rank, name, position, organization, whether they are advisor/principal (if person)

@efo-usds
Copy link
Contributor

efo-usds commented Mar 7, 2017

Users have a need to add new attendees (both principals and advisors) to their reports, as well as locations. This need will increase over time, and it is not something that can be controlled by internal processes (i.e. onboarding and person-tracking) - thus the ability of requesting new additions is core to advisors' ability to submit their reports.

These objects have already been designed and developed (create new person, and create new location). I've repurposed them, presented them in a modal to retain the users' mental model (that of report-writing), and added a brief explanation of what it is they are doing (they're not adding an object, they're requesting it be added to the system by their super user).

New attendee request

This has been updated to match #482
createreport-new-attendee

New location request

createreport-new-location

Note: I've made a global change, all 2-3 option selections will be pills. I'll create a new task to reflect this. Upon direct observation this approach vastly improved a users' experience of the system given that they visualized their choices.

@erincd
Copy link
Contributor Author

erincd commented Mar 13, 2017

created implementation task

@erincd erincd closed this as completed Mar 13, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants