nus-pe-bot
commented
3 years ago Team's Response
We stand by what we view about the uniqueness of the name, because the name of the task can be as specific as possible. For example, given your CS2101 example, the user is expected to write the name of their task as for example: "CS2101 Report" or "CS2101 Demo" for example. If they had two different tasks on the CS2101 report, we expect them to specify "CS2101 Report Introduction", "CS2101 Report Citations" etc. This is because we do not want users to finish a subtask within a task and have to "wait" for the other subtasks within the description to be completed before being able to move their events in the application. This is not what we intended at all, and we intend for users to split their tasks into atomic. singular events, and we feel that a unique name is the best way to go about it. The description simply provides more information about that task but that should not affect the uniqueness of that atomic task.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
Referring to the screenshot, the same could be mentioned about duplicate descriptions, and duplicate descriptions are allowed, but not names? Not sure why this is a valid justification. For example if I had 2 tasks for CS2101, based on the justification both tasks will be described in the description. But what if I am already done with 1 task but not the other? I have to mark the entire task as done?