Status command brings user back to full list after Find command

[Solomon0519]

After using the find command, when we try to edit the status of an application use status function, the application is then reverts back to the full list of companies instead of remaining in the filtered list, this was not mentioned to happen in the User Guide, only for the edit command.

For replication purposes: 1) clear 2) add n/Foo p/6502530000 e/google@gmail.com a/1600 Amphitheatre Parkway, Mountain View, CA 94043 cp/www.google-careers.com r/Interview process takes around 6 weeks t/difficulty_HIGH t/Shopping t/salary_MEDIUM 3) add n/Bar p/6502530000 e/google@gmail.com a/1600 Amphitheatre Parkway, Mountain View, CA 94043 cp/www.google-careers.com r/Interview process takes around 6 weeks t/difficulty_HIGH t/Shopping t/salary_MEDIUM 4) add n/Baz p/6502530000 e/google@gmail.com a/1600 Amphitheatre Parkway, Mountain View, CA 94043 cp/www.google-careers.com r/Interview process takes around 6 weeks t/difficulty_HIGH t/Shopping t/salary_MEDIUM 5) find baz 6) status 1 as/Applied

Maybe similarly for the edit command, could update the DG such that it also says that the application will display the full list after the command

After find bar:

After status 1 as/Applied:

[nus-se-script]

Team's Response

The User Guide specifies that after executing the edit command, the application reverts to the full list of companies. While the status command behavior is not explicitly mentioned, it aligns with this design for consistency across commands that modify company data.

This behavior is not a bug and instead an intentional design choice to ensure users view the entire list after making a modification.

While the behavior of status could be more explicitly mentioned in the User Guide, its omission does not constitute a functionality bug. The lack of detail in the UG represents a minor documentation oversight rather than a significant feature flaw or functionality issue

VeryLow is appropriate because the behavior does not hinder the user's ability to use the application effectively. It is, at most, a minor inconvenience or a matter of user expectation mismatch. The suggestion to clarify this in the documentation could be considered for future updates but does not warrant immediate action.

Items for the Tester to Verify

:question: Issue type

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

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---