VisnuRavi / pe

0 stars 0 forks source link

Done category #4

Open VisnuRavi opened 3 years ago

VisnuRavi commented 3 years ago

After a entry is completed, we enter done identifier, which marks the entry as done and puts it in the done category. However, once an entry is done, it can be deleted away. Keeping it to keep records is not very useful.

Even if this done feature is deemed to be useful to keep done entries, then there should also be an option to add in done items directly through the command box, instead of needing to first put it into a todo/backlog/progress before marking it as done, especially for first time users who may have already done certain tasks before they started using this application. This way they would be able to keep track of what they have done.

nus-pe-bot commented 3 years ago

Team's Response

We feel that this is of low severity at best, since if anyone wants to add events into the done column, it would definitely be a small percentage of people.

Focuris is meant for single-user usage of the kanban board.

For a single user, it does not seem logical for a user to want to add tasks that have already been completed beforehand into the done column, since if it's done and submitted, they could simply move on and add other tasks that need to be tracked, rather than ones that are already completed.

If this were a tool used across several teams, perhaps being able to add tasks into done could be more intuitive such that supervisors are able to track their subordinates' work, but again, if it's already completed, there doesn't seem to be a need to add it into a kanban board unless they have been tracking the progress, from backlog or todo or in progress.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: The team has not answered my initial question of using done to delete away the completed entry record, instead of keeping the entry, and then needing the user to manually input another command to delete the completed entry. It does not seem very optimised for the user.


:question: Issue severity

Team chose [severity.Low] Originally [severity.High]

Reason for disagreement: Perhaps a medium is more appropriate, as many users would face this when moving a task to done, only to then delete it, and be inconvenienced.