Team's Response

The sort command works fine after the find command.

The find command filters the list based on some properties, and returns the filtered list. Then the sort command will sort the filtered list instead of the original list without any issue, you can try it out on the AgentSee application.

In your case, you used find with properties that no client holds, so you end with no clients. Therefore if you try to sort with an empty client list, it will return nothing.

If you wrongly think that the data is deleted, you can use the list-s or list-b command to clear your doubts.

Though in user guide it says 'sort all buyers', it should be interpreted as 'sort all buyers in the displayed list'. The ambiguity of words in user guide should not be considered a functionality bug.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

[x] I disagree

Reason for disagreement: The team writes that the sort function works as they expect it to. However, I think that this issue is still a bug that was not highlighted or addressed anywhere in the UG especially since the UG writes (and the team pointed out): "Sort all the buyers". If what I encountered was the expected and correct behaviour for a user, then the team would not have had to explain that their UG is misleading.

Furthermore, I think that if the team has to suggest that a reader should interpret their UG in a different way, then there is a definitely a bug, and they cannot reject this issue. Thus, I agree that there is at least a documentation bug present, but I do not think this issue should be rejected.

:question: Issue type

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

[ ] I disagree

Reason for disagreement: [replace this with your explanation]

:question: Issue severity

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

[ ] I disagree