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

Index-based commands can be used without list after find command is called #7

Open
julia-cp opened this issue Apr 19, 2024 · 1 comment

Comments

@julia-cp
Copy link
Owner

julia-cp commented Apr 19, 2024

Screenshot 2024-04-19 at 5.18.04 PM.png
Steps to reproduce:
type find david
type edit 1 n/Gracia

Expected: unintended outcomes for index-based commands. (edit, delete, etc.)
Actual: outcome executed correctly
Screenshot 2024-04-19 at 5.20.08 PM.png

Most users will lose a lot of time by following these steps in the user guide.

@nus-se-bot
Copy link

nus-se-bot commented Apr 22, 2024

Team's Response

This could be a misunderstanding with regards to the UG, as what we meant is that indexes are based on the currently listed persons, and the disclaimer is to rectify confusion for users that assume indexes are based on the fully listed contacts (using "list" command)

Items for the Tester to Verify

❓ Issue response

Team chose [response.NotInScope]

  • I disagree

Reason for disagreement: Screenshot 2024-04-23 at 6.54.06 PM.png
This issue does not qualify as NotInScope.

Based on the team's response, the user guide disclaimer is not the same as what restriction they intended the feature to have.
No part in the UG specifies it as not supported or coming in a future version, this is just a mistake in writing the UG.
The user can also attempt to use the feature, and it doesn't fail (which is the expected outcome).

This means this issue misses both criteria to consider this as NotInScope.


❓ Issue severity

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

  • I disagree

Reason for disagreement: find is a common command that most users will use. This issue will cause occasional inconvenience to most users.
Therefore it should be severity.Medium.


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