nus-pe-script
commented
1 year ago Team's Response
Thanks for the suggestion! Our team acknowledges that the sorting order of empty deadlines can cause inconvenience and it would be better to place them at the top or bottom of the list. However, the application already separates the projects with deadlines from those without, and thus can still scroll past the empty deadlines and access the other projects with deadlines. It is also clearly stated that the project has "No deadline" and the user is very unlikely to misunderstand that projects with no deadlines have deadlines shorter than others. Furthermore, most projects in a company consist of a deadline and it is not very common for our target users to be using projects with no deadline, therefore it only causes minor inconvenience and should be of 'Low' severity rather than 'Medium'.
Items for the Tester to Verify
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [x] I disagree
Reason for disagreement: The Team has made a huge assumption that their target users (developers) would generally be working on projects that have a hard deadline. This is not true as the there are many developers who do not have hard deadlines set for the entire project at the very beginning of their projects. Rather, they would have hard deadlines for the sub components (or subsections) of the projects that they have been assigned to. The hard deadline for the entire project will then be deliberated on based on the rate of the initial progress that's been made, in consultation with the internal/ external clients. As such, it is very possible to have numerous projects without hard deadlines.
Given that users would regularly want to view the projects with the earliest deadlines to have a quick overview of the urgent projects that are upcoming, they are likely to use the project -s d/0 command frequently to sort the projects from shortest/ closest deadlines to longest deadlines. Having to scroll past a long list of projects without a deadline before viewing the list of projects with the shortest deadline (even if they do not misinterpret it as having a shorter deadline) will inconvenience a large portion of our users. The inconvenience occurs frequently given how often the developers will typically use this command.
Hence, this issue should be of Medium severity.
When sorting by date, project -s d/0 allows the projects without deadline to remain at the top
while project -s d/1pushes the projects without deadline to the bottom of the list
This implies that projects without deadline have a "shorter deadline" that any project with a deadline. Projects without deadline should consistently be at the top or at the bottom of the list regardless of d/0 or d/1 and should not be sorted with the rest of the projects that have a deadline.