Easy to mix up PERSON_NUMBER and TASK_NUMBER in `atask` and `unatask` command format

[LowXiSi]

Since command formats are atask PERSON_NUMBER TASK_NUMBER and unatask PERSON_NUMBER TASK_NUMBER, user may easily mix up the positions of PERSON_NUMBER and TASK_NUMBER, which will inconvenience the user.
e.g. For atask 3 4, it is not immediately obvious if task 3 should be assigned to person 4 or task 4 should be assigned to person 3

[nus-se-bot]

Team's Response

Our user guide explains the differences between the parameters and, similarly, so does the error response when the user uses the command incorrectly. Hence, this is not a bug.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: I believe this is a case where the feature could be better, and is an easy fix.

With the current format, the user has to memorise the command format to know whether PERSON_NUMBER or TASK_NUMBER should come first, which may prove difficult given that there are a total of 28 commands available within this app, mostly with different formats. If they are unable to remember to be sure, they would likely have to refer to the command format in the user guide every time they use atask or unatask. This causes inconvenience to users, as they would want to be able to operate with the app with minimal reference to the user guide once they reach a certain level of familiarity.

In the scenario where the user remembers the command format wrongly, for example they want to assign task 1 to person 2 and enters atask 1 2 (the correct command is atask 2 1), the command may still successfully assign task 2 to person 1. Now that the user notices that the assignment was wrong and has to rectify it using unatask, they face the same dilemma and has to check the user guide this time to be sure of which number comes first.

Differentiating between the parameters could be as simple as adding prefixes such as atask person/3 task/4 hence I believe this is an easy fix, or at the very least, something that could be improved in the future to enhance the user experience.

---

❓ Issue severity

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

• I disagree

Reason for disagreement: [replace this with your explanation]

---