Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The Finalise Projects screen is not particularly well-designed #14

Open
2 tasks done
sersorrel opened this issue Aug 5, 2019 · 1 comment
Open
2 tasks done

The Finalise Projects screen is not particularly well-designed #14

sersorrel opened this issue Aug 5, 2019 · 1 comment
Labels
user-testing This was filed because of user testing UX/UI This is to do with how the application looks or behaves.

Comments

@sersorrel
Copy link
Contributor

sersorrel commented Aug 5, 2019 •
edited
Loading

  • 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 (see componentDidUpdate in Projects for 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.
@sersorrel sersorrel added user-testing This was filed because of user testing UX/UI This is to do with how the application looks or behaves. labels Aug 5, 2019
sersorrel added a commit that referenced this issue Aug 6, 2019
@sersorrel
Show more detail in finalise choices screen
daebd8f 
The supervisor and project type (computational/wetlab) are now shown
after each project title.

This also adds support for a class ".btn-long" which can be used to
modify the styling of a button that is expected to contain long text,
which makes the button's content wrap over multiple lines.

See #14.
sersorrel added a commit that referenced this issue Aug 28, 2019
@sersorrel
Display which users a choice conflicts with on the finalisation screen
77fe312 
Previously, if a conflicting choice was made, the two offending rows
would turn BRIGHT RED, but no other feedback was visible -- since the
other row would frequently be scrolled off the screen, this is not
exactly the most helpful way the application could tell the user that
something is wrong ("you did something wrong, but I'm not going to tell
you what it is").

Now, the name of the user(s) with which a choice conflicts is/are
displayed on the right-hand side of the table. That space is reserved
even if there is currently no conflict, since having the table jump
around underneath you if you choose a conflicting project is even worse
than the existing behaviour!

See #14.
@sersorrel
Copy link
Contributor Author

The name of the user with which a choice conflicts is now displayed:

screenshot of "Finalise Choices" screen

(previously the offending rows just turned red, which is not helpful if the other row is way offscreen)

sersorrel added a commit that referenced this issue Aug 29, 2019
@sersorrel
Prompt user before discarding changes from finalisation screen
46f1058 
This isn't an ideal solution; it would probably be better to just
automatically save choices as they're made. However, saving assignments
makes them visible to students, which isn't ideal.

Hopefully we will display enough information directly on this page that
users won't need to navigate away, so this prompt will never be seen...

See #14.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
user-testing This was filed because of user testing UX/UI This is to do with how the application looks or behaves.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sersorrel