nus-pe-bot
commented
4 years ago Team's Response
It is the expected behaviour. Since the tasks created by the scheduler has a priority value of 0, we wanted to provide the user a choice to create tasks with both higher and lower priority than the scheduled tasks.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I understand your rationale in allowing the flexibility of the priority value of tasks.
However, I feel that a more meaningful metric could be used (for e.g. using number scale 1 - 10). At the same time, having negative values would also mean that the user must decide, how much priority a task needs to given.
For instance, if the program stores a lot of tasks previously, the user would have to list the tasks to check the negative values (on top of tasks with positive priority values), and judge accordingly before assigning a priority score to the task he/she now wishes to add. A fixed number scale would have make it more user friendly and simple.
That said, this is a concern that I think can help benefit the user in the long run. After all, the usage should be easy to use.
From the image below, it seems that a user can supply a negative priority score. The negative priority score does not seem appropriate.