Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2a should be use case ends #50

Open
Winniehyx opened this issue Apr 16, 2021 · 1 comment
Open

2a should be use case ends #50

Winniehyx opened this issue Apr 16, 2021 · 1 comment

Comments

@Winniehyx
Copy link
Owner

Winniehyx commented Apr 16, 2021

No details provided.
image.png

@nus-pe-bot
Copy link

nus-pe-bot commented Apr 20, 2021

Team's Response

No response provided.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Use case 2a does not end

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.



image.png


[original: nus-cs2103-AY2021S2/pe-interim#401] [original labels: severity.Low type.DocumentationBug]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

No response provided.

Items for the Tester to Verify

❓ Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

  • I disagree

Reason for disagreement: This is not a duplicate of the other issue. The other issue is on another use cases and it should not be lumped together as they are different. Mine is on how the use case should not continue and the other is on the absence of use case end wording.


❓ Issue severity

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

  • I disagree

Reason for disagreement: I agree that severity should be lowered but perhaps to a medium as if users/developers refer to the use cases to try out the command, they are not sure when the use case ends and would think that the use case continues, which leads to confusion.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants