`unatask` should be able to take in name of task instead of just task number

[LowXiSi]

There is an additional step of list-tasks, followed by scrolling through the tasks to find the exact task to unassign from the person. This can be very inconvenient and take a long time when there are a lot of tasks created. Since only tasks currently assigned to the person can be removed, the user should be able to only look at the person's task list when unassigning tasks. This is not much harder to implement and would be much more convenient to the user.

[nus-pe-bot]

Team's Response

The correct usage of the unatask command is with the task number within each person's task list, which a user would not have to execute list-tasks to find. It is also much faster to type in a number rather than the name of the task and much less error prone. The behaviour is as stated and expected, so this is not a bug.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: I admit that I have misunderstood the command format for unatask, however my concern still stands as I believe the command format of unatask inconveniences the user.
It is confusing that atask 1 2 refers to assign the second task in the entire task list to person 1,
but unatask 1 2 refers to unassign the second task within person 1's assigned tasks.
The inconsistency between the two command formats despite them being remarkably similar, added with the fact that the two commands are highly connected (unatask can be considered the undoing of atask), makes this an easy mistake to make for the user. In this case, there is even more reason to use the task name instead of task number to remove all ambiguity in the command.

---