bernarduskrishna / pe

0 stars 0 forks source link

Same alias for different commands should warn the users at the very least. Currently it replaces old alias with current alias. #8

Open bernarduskrishna opened 2 years ago

bernarduskrishna commented 2 years ago

image.png

nus-pe-bot commented 2 years ago

Team's Response

No details provided by team.

The 'Original' Bug

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

Creating alias with same name as existing alias will overwrite the current alias.

image.png

After creating an alias (alias add addnew) and then creating another alias with the same name (alias delete addnew), it simply replaced the old alias with the new one (see screenshot above). This was not clearly stated in the UG and could confuse users. An error message would have been appropriate, perhaps prompting the user that such an alias already exists and asking if they would like to overwrite it.


[original: nus-cs2103-AY2122S1/pe-interim#3687] [original labels: type.FunctionalityBug severity.Medium]

Their Response to the 'Original' Bug

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

Thanks for pointing this out. You have a fair point that the user may be confused about this, as we also did not state it in our UG. However, I believe that the severity level should be lower, as it does not have significant impact on the user. No contact data is loss. The alias that was overridden could be re-added easily by the user. Moreover, the most recent alias created will be the one that the user remember the most.

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]


:question: Issue type

Team chose [type.FunctionalityBug] Originally [type.FeatureFlaw]

Reason for disagreement: [replace this with your explanation]