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

Teacher should be able to find stuck or errorneous submissions more easily #793

Open
markkuriekkinen opened this issue Mar 8, 2021 · 1 comment
Open

Teacher should be able to find stuck or errorneous submissions more easily #793

markkuriekkinen opened this issue Mar 8, 2021 · 1 comment
Labels
area: exercises Related to exercises. Use other labels to focus issue to UI/backend area: UX teacher User experience and usability for teachers effort: days Estimated to take less than one week, from the creation of a new branch to the merging experience: beginner required knowledge estimate requester: CS The issue is raised internally by a CS teacher requires: discussion Requires discussion before it is possible to proceed to implementation requires: priority Currently using this label to flag issues that need EDIT decision ASAP (even if there was priority) type: feature New feature or change to a feature

Comments

@markkuriekkinen
Copy link
Contributor

If the submission is in the error status or it seems to be stuck in the waiting or initialized status, the teacher should be able to find those submissions more easily so that the teacher could do something about them. The teacher might also benefit from easy-to-understand notifications about these error cases.

Internal ticket: https://rt.cs.aalto.fi/Ticket/Display.html?id=18426
@markkuriekkinen markkuriekkinen added area: exercises Related to exercises. Use other labels to focus issue to UI/backend area: UX teacher User experience and usability for teachers effort: days Estimated to take less than one week, from the creation of a new branch to the merging experience: beginner required knowledge estimate priority: medium Valid issue, good to fix but cannot be scheduled yet requester: CS The issue is raised internally by a CS teacher type: feature New feature or change to a feature labels Mar 8, 2021
@markkuriekkinen markkuriekkinen added the requires: discussion Requires discussion before it is possible to proceed to implementation label Mar 8, 2021
@markkuriekkinen
Copy link
Contributor Author

The exercise submission list page has been improved in recent releases (A+ v1.12). The list page includes search/filter feature and sorting in each column. However, there is no overview of all assignments in the course if the teacher particularly wants to find all stuck submissions.

Related to mass regrading #470, #960 and #972.

@markkuriekkinen markkuriekkinen added requires: priority Currently using this label to flag issues that need EDIT decision ASAP (even if there was priority) and removed priority: medium Valid issue, good to fix but cannot be scheduled yet labels Feb 15, 2022
This was referenced Feb 15, 2022
Closed
Closed
@jkotimak jkotimak mentioned this issue Oct 10, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area: exercises Related to exercises. Use other labels to focus issue to UI/backend area: UX teacher User experience and usability for teachers effort: days Estimated to take less than one week, from the creation of a new branch to the merging experience: beginner required knowledge estimate requester: CS The issue is raised internally by a CS teacher requires: discussion Requires discussion before it is possible to proceed to implementation requires: priority Currently using this label to flag issues that need EDIT decision ASAP (even if there was priority) type: feature New feature or change to a feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@markkuriekkinen