nus-pe-bot
commented
3 years ago Team's Response
Thank you for your suggestion. Unlikely to implement does not equate to us not implementing it at all. We gave it our best shot so we tried our level best to implement as many features as we could.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Future developers would read the use case and see that it is marked as unlikely to implement, but they would be confused as to why it is implemented despite the priority marking. It is good for the team to implement as many features as they could, but perhaps the priority marking should be changed to nice to have.
:question: Issue severity
Team chose [severity.VeryLow]
Originally [severity.Low]
- [x] I disagree
Reason for disagreement: It is not purely cosmetic. It causes confusion for the future developers as they would not be sure what to implement next as the team gave some inconsistencies on the priority marking in the user story and the actual implementation, but would unlikely affect normal operations. Therefore, it is a Low
User stories marked as unlikely to have but is implemented e.g.
tag,edit,find, etc