search

zeonchew0324 / pe

0 stars 0 forks source link

Error thrown when edit people /r cannot clear roles #8

Open zeonchew0324 opened 1 week ago

zeonchew0324 commented 1 week ago

Error message with the wrong info thrown to user when user tried to clear roles of people as per user-guide.

Bug 8a.png

Bug 8b.png

nus-se-script commented 1 week ago

Team's Response

No details provided by team.

The 'Original' Bug

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

Edit Command Does not work for modifying certian fields

Description In the UserGuide, the edit command allows one to edit the fields of the respective person as stated below and says at least one of the fields must be provided image.png

However, when i try to edit the fields, it doesn't work


video:https://raw.githubusercontent.com/nus-cs2103-AY2425S1/pe/master/files/6e50ea4d-97cf-4a1f-94ea-5a38273bc0e6.mp4

Commands tested:(some are not displayed in the video, but it still doesn't work) edit 1 r/vol-photo edit 1 p/12345678 edit 1 r/ edit 1 e/test@123.com

Expected result: i should be able to modify the fields the person of the first index.

Actual result: given the prompt of invalid command format

Explanation on the severity This issue critically affects the app's usability, as it blocks users from modifying existing person records. The inability to update roles or other details significantly limits the app's functionality

This bug prevents users from updating essential details of participants, such as their roles, which is a core feature of EventfulNUS, particularly for managing dynamic events where roles and participant details frequently change.

Given the organiser of large events like IFG, it is almost impossible to not make any changes, hence severely affecting the normal usage.

To add on, The error message "This person already exists in the address book" is misleading and does not provide helpful feedback

[original: nus-cs2103-AY2425S1/pe-interim#883] [original labels: severity.High type.FunctionalityBug]

Their Response to the 'Original' Bug

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

Thank you for this bug report. We agree that this is a high-severity Functionality Bug and, hence, decide to accept it.

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 severity Team chose [`severity.High`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]