-
Notifications
You must be signed in to change notification settings - Fork 1
The Finalise Projects screen is not particularly well-designed #14
Copy link
Copy link
Open
Labels
UX/UIThis is to do with how the application looks or behaves.This is to do with how the application looks or behaves.user-testingThis was filed because of user testingThis was filed because of user testing
Description
-
the supervisor's name needs to be shown for each project -
each project's computational/wetlab status needs to be shown the red background for conflicting users is unexplained, and caused surprise when trying to swap which projects two users were assigned to- the Save button is hidden at the bottom of the page,
and navigating away from the page without saving can lose a significant amount of work - it's important for the person assigning projects to know the number of students assigned to each supervisor (in order to avoid giving any one supervisor an overly-large workload); this data isn't exposed anywhere, but could be
- the Graduate Office can inadvertently assign someone to a computational project when they are required to complete a wetlab project, or vice versa – this data is kind of tricky to get at from the
ChoiceEditor(seecomponentDidUpdateinProjectsfor how it's calculated elsewhere)
In general, this screen assumes that the user already knows what their desired end-state is and wants to tell the system what to do as quickly as possible, whereas in reality there is a nontrivial amount of thought put into project allocation, and showing the user a little more information would make the process significantly easier.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
UX/UIThis is to do with how the application looks or behaves.This is to do with how the application looks or behaves.user-testingThis was filed because of user testingThis was filed because of user testing