Open jolynloh opened 1 year ago
No details provided by team.
[The team marked this bug as a duplicate of the following bug]
Misleading documentation for adding a new deadline to tasks
User Guide states that d/NEW DD-MM-YYYY should be used for adding a new deadline, misleading users on whether they should be adding "NEW" into the output (if the NEW was part of the description of the output, it should be hyphenated with DD-MM-YYYY, i.e. NEW-DD-MM-YYYY or NEW-DEADLINE)
[original: nus-cs2103-AY2223S1/pe-interim#1993] [original labels: severity.VeryLow type.DocumentationBug]
[This is the team's response to the above 'original' bug]
No details provided by team.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
Reason for disagreement: [replace this with your explanation]
Team chose [type.DocumentationBug
]
Originally [type.FunctionalityBug
]
Reason for disagreement: [replace this with your explanation]
Team chose [severity.VeryLow
]
Originally [severity.Medium
]
Reason for disagreement: From the perspective of a reader of the UG, I genuinely mistook NEW
as a command I had to input along with DD-MM-YYYY
. Hence, it feels like this is more than a severity.VeryLow cosmetic issue/typo as it has affected usage, causing occasional inconvenience as users are unable to properly use this command whenever they want to, though it is possible to continue with the usage of the other commands (which is exactly the definition of a severity.Medium type label). It takes an astute reader to realise that NEW
is not a command to be inputted but just a "description" of the "new" date entered into the command.
Following the underlined instruction gives an error message
Instead, it seems that using the command without the
NEW
part of the d/ tag works just fine