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.

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

Improve UX of evaluations #4173

Open
Tracked by #4364
jorg-vr opened this issue Nov 18, 2022 · 0 comments · May be fixed by #5636
Open
Tracked by #4364

Improve UX of evaluations #4173

jorg-vr opened this issue Nov 18, 2022 · 0 comments · May be fixed by #5636
Assignees

Comments

@jorg-vr
Copy link
Contributor

jorg-vr commented Nov 18, 2022

During the UI/UX course I user tested the evaluations workflow

It was only a single test, but already made clear some obvious issues.

  1. Given the task to grade the exercises of students, the participant searched for a way to export the solutions and grade them there. He saw the 'evaluate series' button and dismissed it as unhelpful for his task.
  • I think naming might be an issue here
  1. We helped him make an evaluation. But on the evaluation page he was unable to find how to grade a student.
  • First he tried clicking on the exercise links. Expected behavior: Go to a page were he can start grading this exercise
  • Then he tried clicking on student names: Expected behavior: Go to a page were exercises for this student can be graded
  • He did look at the icons in the details table, and after some deduction he figured out what they might mean, but never figured out these symbols are also buttons.
@jorg-vr jorg-vr added the enhancement A change that isn't substantial enough to be called a feature label Nov 18, 2022
@bmesuere bmesuere added this to Roadmap Nov 18, 2022
@bmesuere bmesuere moved this to Unplanned in Roadmap Nov 18, 2022
@jorg-vr jorg-vr self-assigned this Jun 24, 2024
@jorg-vr jorg-vr linked a pull request Jun 24, 2024 that will close this issue
1 task
@bmesuere bmesuere removed the enhancement A change that isn't substantial enough to be called a feature label Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Unplanned
Development

Successfully merging a pull request may close this issue.

2 participants