angsongyee / pe

0 stars 0 forks source link

Flaw in managing assignments #4

Open angsongyee opened 5 months ago

angsongyee commented 5 months ago

image.png

Looking at the descriptions of the adda and removea commands, it is mentioned that these commands are applied on all students at the same time. This makes sense, as students in the same course usually have the same assignments. However, when a new user is added, they are not given any of the current assignments, and the user will have to run adda to update their assignments manually. This creates a situation where the user constantly has to check if all students have their proper assignments, which poses a major inconvenience. Thus, it would be better if assignments were managed on a class/course level, and also for new students to automatically receive any existing assignments.

Steps to reproduce:

  1. Ensure at least one student exists in the app.
  2. Run adda a/PE
  3. Run add n/Danielle Marsh e/daniellemarsh@u.nus.edu m/A9876543Z tl/danimarsh12 (assuming this user is not already in the list)

Expected Behavior: New user receives current assignments.

Actual Behavior: New user is created without any assignments.

image.png

nus-se-bot commented 5 months ago

Team's Response

Possible improvement but not what was promised within scope of UG. Might implement in the future. Severity changed to Low since it does not affect usual operations, since students are unlikely to be added to a class after assignments have been created. Minor inconvenience for users.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: [replace this with your explanation]


## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]