nus-se-script
commented
2 years ago Team's Response
No details provided by team.
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Add todo to project doesnt check for duplicates
Multiple todo of the same names are allowed
[original: nus-cs2113-AY2122S2/pe-interim#1218] [original labels: severity.Medium type.FunctionalityBug]
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 explanation]
:question: Issue type
Team chose [type.FunctionalityBug]
Originally [type.FeatureFlaw]
- [x] I disagree
Reason for disagreement: [replace this with your reason]
Your team probably chose not to have this feature considering the relative ease of implementation, thus it shouldnt be a functionality bug and it's very likely a deliberate design choice by your team.
:question: Issue severity
Team chose [severity.Medium]
Originally [severity.Low]
- [x] I disagree
Reason for disagreement: [replace this with your reason] As a design choice, it doesn't suitable.
Given the nature of the projects seem largely coding project related, I feel having duplicate todos with duplicate deadlines do not make sense.
E.g. let wwefeefwef be code review. There can be daily code reviews, but not the same code review on the same day (there's no mention of time of day).
A recommendation would be to at least prompt for such duplicates before user confirms, or prevent users for creating such confusing todos