Open XindiTian opened 3 years ago
No response provided.
[The team marked this bug as a duplicate of the following bug]
Use Case Numbering
Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.
The extension should start from where the command is keyed in (i.e.2a
should be1a
since the error is triggered by step 1)
[original: nus-cs2103-AY2021S2/pe-interim#2761] [original labels: severity.Medium type.DocumentationBug]
[This is the team's response to the above 'original' bug]
No response provided.
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]
Wrong numbering in all use case extensions,
The last one has a mismatch in use cases numbering.