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

UG does not specify that datetime cannot be repeated #6

Open
sdevih opened this issue Apr 19, 2024 · 1 comment
Open

UG does not specify that datetime cannot be repeated #6

sdevih opened this issue Apr 19, 2024 · 1 comment

Comments

@sdevih
Copy link
Owner

sdevih commented Apr 19, 2024

Description

The UG for add feature, nor the part of features, does not specify that the same datetime cannot be repeated across students, so explanation for add feature is too brief and should include more constraints regarding what can be allowed.

Steps to reproduce

add n/John Doe p/98765432 e/[email protected] a/311, Clementi Ave 2, #2-25 g/A s/Mathematics at/Present pa/Paid nt/Sample note d/2024-03-02 1800

Screenshot

image.png

image.png

@nus-pe-script
Copy link

nus-pe-script commented Apr 22, 2024

Team's Response

Thank you for your inputs. It indeed woud be beneficial to notify users that datetime duplicates will not be accepted in order to not having conflicting sessions. However, this should be a very low severity instead of medium as user can still use the app as per normal with rare cases of conflicting sessions.

Items for the Tester to Verify

❓ Issue severity

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

  • I disagree

Reason for disagreement: Thank you for your response.

I politely disagree with the bug's reduction of severity to veryLow.

According to the tP instructions, a bug of severity veryLow is only given to a flaw that is purely cosmetic and does not affect usage such as a typo/spacing/layout/color/font issues in the docs. However, this constraint that the datetime cannot be repeated across students is not a cosmetic issue. Instead, it is an issue that can actually occur when users input conflicting date time for the students being added and as such, this behaviour should be noted in the user guide as not allowed under the "add feature".

With that said, I do believe the bug severity can be classified as low, based on how the team has responded to the bug that these conflicting sessions only occur rarely. However, since the team has chosen veryLow instead of Low, I believe that the bug should be changed to severity low.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants