Inconsistent display after deleting a person

[Xzh119]

Description: If I view a person first and deleting that person. It will automatically do the things like a view command to display another person's information. In this situation, if the person I deleted is the first person, it show the person behind him. Otherwise, it show the person in front of him.(In a ten people list. You can do view 1 ,delele 1 and view 7 delete 7 to check) Besides, Iy you do not view a person first then delete one, app will not display any person information. This will be quite confusing for users and in UG , most of the screenshots after deletion is no display.

Suggestions: Modify the UG to state this situations clearly delete comman.

[nus-se-script]

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

Hi!

This seems more like a documentation bug as we intended it to simply display the next person's information after one is deleted. However, the UG does not clarify that this is the expected behavior. We will update the documentation to match this behaviour.

Thank you.

Items for the Tester to Verify

❓ Issue type

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

• I disagree

Reason for disagreement: Hi!

The current behavior — where the application only shows the next person's information after deletion if the user has previously viewed that person — is confusing and unintuitive from the end-user’s perspective.

From a user experience point of view, the current inconsistency (sometimes showing another person if the deleted person was viewed first, and sometimes showing nothing if they were not) may lead users to believe that the deletion was unsuccessful or that something is broken. Additionally, as I have mentioned above, the identity of the next person shown after deletion is also inconsistent depending on which index is deleted. From a usability standpoint, automatically showing another person after deletion is not necessarily more intuitive. In fact, it may be more natural and less confusing if the application simply performs the deletion and does not display any other person's information. This results in a more intuitive and consistent delete experience for the user.

Furthermore, fixing this issue — for example, by not displaying another person after a deletion — would not require significant additional effort. According to the official definition of FeatureFlaw bug from the website:
"If the feature is implemented to work in a certain way but it could have been implemented to work in a better way (from the end-user's point of view) without much additional effort,"

I just make it a low severity of FeatureFlaw bug. Making the documentation overly complicated just to cover different situations may come across as an attempt to justify or patch over unintuitive behavior, rather than addressing the root problem from a user-centric design perspective. Instead of relying on extensive explanations to clarify inconsistent behavior, it would be better to refine the feature itself so that it works in a more predictable, consistent and intuitive way of deletion for the user. So it should be more of a FeatureFlaw bug.

I hope this explanation makes sense and that you can accept my bug as it is. Thank you!

---