nus-pe-bot
commented
11 months ago Team's Response
No details provided by team.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Allows appointment time with 0 minutes
Appointments with 0 minutes isn't feasible in real life.
[original: nus-cs2103-AY2324S1/pe-interim#3897] [original labels: type.FunctionalityBug severity.High]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
We allowed for users to have appointment start time and end time be the same so as to allow for appointments where a user may not know when the end time is or simply for very brief appointments. The only constraint our UG mentions is that the end time cannot be before the start time and even that the start and end time can be the same(as shown in the screenshot from our UG below). If we were to prevent appointments from being 0 minutes long, then is 1 minute too short as well? Where would we draw the line? Hence we allow this so that the receptionists have the full flexibility.
Hence we feel that this should not be a bug.
The bug type is also certainly not a functionality bug since the actual behaviour is not different from the expected behaviour but rather a feature flaw.
With this we propose to label it as Not In Scope, with the enhancement being to warn users when an appointment with 0 minute is added.
As for severity, this should certainly not be a high as it does not make the application unusable for most users. In fact this is unlikely to affect normal operations of the product and should be of Low severity
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
## :question: Issue response Team chose [`response.NotInScope`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
It does not make sense for an appointment to have the same start and end time. This should be handled by the application and the user should not be able to do so.