nus-se-bot
commented
6 months ago [IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]
Team's Response
No details provided by team.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
App allows user to edit the current schedule name into name that already exist in that person
App allows user to edit the current schedule name into name that already exist in that person. This should not be allowed
[original: nus-cs2103-AY2324S2/pe-interim#3813] [original labels: type.FunctionalityBug severity.Low]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
No details provided by team.
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 reason]
## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.DocumentationBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your reason]
From the UG, addSched 1, 2, 3 s/CSMeeting start/2024-03-18 13:00 end/2024-03-18 19:00 will add the 1st, 2nd and 3rd persons in the address list to the CSMeeting event which would take place on 18th March 2024 from 3pm - 7pm.
But, in the potential errors, error can occur when duplicate Schedule with the same name is added to the same person. This part should be more clearly explained in the UG.