jiakai-17 / pe

0 stars 0 forks source link

app: Difficult to delete courses with long names #4

Open jiakai-17 opened 8 months ago

jiakai-17 commented 8 months ago

app: Difficult to delete courses with long names

Affected Component(s)

[x] Application [ ] User Guide [ ] Developer Guide

Description

Deleting a course requires knowledge on its full module code.

If a course code is long, it is difficult to enter the full code to delete the course.

Moreover the does not provide a quick way to get a full course code

Steps to reproduce

  1. Create a course with long code
  2. Try to delete the course again

Command(s) entered:

course create course/210933333333333333333333333333333333333333333847479749873298473219743297432

Expected behavior

Some way to delete a course without knowing its full course code

Actual behavior

Need to enter the full course code.

Screenshots, if any

image.png

Additional context / Potentially problematic behavior / Improvements

[x] I have checked that this has not been addressed in the Planned Enhancements of the Developer Guide.

Reason for choosing severity level:

nus-pe-script commented 8 months ago

Team's Response

Firstly, in our DG, it is clearly stated that our product is scoped for TAs in NUS teaching Computer Science courses.

Secondly, this would not be applicable when validation checks for course codes are added in a future version, as NUS course codes are usually 6-8 characters long, and hence there would not be an instance of "long course names". This is Planned Enhancement #3 in our DG.

Since it is a problem solved by a Planned Enhancement, we consider this bug report to be invalid.

Additionally, even if we disregard the Planned Enhancement, the team does not think that there should be an expectation to delete courses easily, as deleting courses is a feature that would cause a large amount of data to be lost (all students in the course would be deleted). As such, we believe that it is extremely important that the course code entered by the user matches the course code exactly, as a way of "confirming" the deletion. Deletion by index or via a partial match would likely lead to accidental loss of data, and is greatly undesirable.

We believe that this bug report is invalid considering our Planned Enhancements, and we also do not think that this is a valid feature flaw. Hence, we have rejected this bug report.

Note: We have also clarified with Prof in the forum, over the handling of this bug reported (link). Since there is clear evidence in our DG that our target user profile refers to NUS TAs teaching CS courses, we have evaluated this bug report based on it.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

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]