Open Daviancold opened 5 months ago
urgent task are only for the future task that has not been started yet.
Team chose [response.Rejected
]
Reason for disagreement: I understand that that might have been the consideration when designing the feature.
User Guide for the Urgent Task Feature
However, this was not mentioned in the user guide, and as a user, I might interpret the term urgent
differently. What if I used this application to store an upcoming meeting which I might have with someone else (as it was intended) but I forgot about it and was late to it? Surely this meeting should be classified as urgent since I might still be able to make it for the rest of the meeting?
However, seeing as to how this feature is not broken, I was just merely pointing out a flaw in the feature, hence this bug is a FeatureFlaw
bug, and I believe it is justified and should not be rejected.
Time as of bug reported: 1658H Time of Task added: 1600-1800H
The task is still ongoing, but is no longer counted as urgent. Perhaps it can be considered as an urgent task, rather than only consider tasks that have not occurred yet.