albertsutz / pe

0 stars 0 forks source link

Cannot edit Student Number of existing person #8

Open albertsutz opened 2 years ago

albertsutz commented 2 years ago

image.png

Note that there is no existing contact with "A8888888U"

nus-pe-bot commented 2 years ago

Team's Response

Hi, the team has chosen to downgrade the severity of this bug to Severity.Low. We acknowledge the bug and are disheartened by its presence.

Our reasons for not accepting it at a medium severity are listed below:

Severity Low is defined as "A flaw that is unlikely to affect normal operations of the product. Appears only in very rare situations and causes a minor inconvenience only." and we believe this is what is applicable here as well.

As the developing team, the import-csv command was implemented to optimise getting tasks done faster for the user. Our recommended mode for creating your student list is by using import-csv and this method is undoubtedly less prone to (data-entry) errors if the file is exported from LumiNUS. We don't expect there to be much, if at all any, need for editing a student number since the information provided by LumiNUS will be accurate.

Going down the same path, manual addition of students is projected to be in rarer situations and if the user made an error in the process then yes, as pointed out, our application has a bug.

Nonetheless, if we look at TAilor on a whole, there aren't many commands that are dependent on the student number attribute of a Student. In our User Guide, we mention the following for the mail-x command:

image.png

The only situation where you could need to use the matriculation number is when you want to find one particular student. This process may be hindered due to the wrong student number being entered in the first place (and the edit option being buggy), however, we have a functional alternative which is to find using the unique email address.

Situation reproduced on our end:

image.png

Looking at the chances of this situation occurring, inconveniences being caused (while using other commands), and functional alternatives, we are happy to accept this bug at low severity.

Items for the Tester to Verify

:question: Issue severity

Team chose [severity.Low] Originally [severity.Medium]

Reason for disagreement: [replace this with your explanation]