Different Behavior for Adding a Person (Unsorted v.s. Sorted List)

[wkxcass]

Adding a person gives different behaviors, with an unsorted versus a sorted list.

If the contact list is initially unsorted, the person below will end up being added to the end of the list:

If the same original contact list was sorted first,

the person below will end up being added to its corresponding position according to the last sorting-sequence:

[nus-se-script]

Team's Response

This is not incorrect behavior. Because after sorting the list, the list will be maintained in a sorted order. As such, any addition of a person will be put into their corresponding positions. As for unsorted list, since there is no need to maintain the list in a sorted order, the person will be added to the bottom of the list by default.

Items for the Tester to Verify

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: Thanks for the clarification above!

With that, I would suggest classifying this issue as response.NotInScope. After some rethinking, I believe that this would be more related to a documentation flaw (can't propose changes on this label for now, just to mention). The logic above could be addressed in the UG to further clarify the functionality of the program, which may be slightly confusing for a minority of first-time users (like me🙏).

---

❓ Issue severity

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

• I disagree

Reason for disagreement: [replace this with your explanation]

---