Editing job in a filtered list returns to the unfiltered list

[Singa-pirate]

Steps to reproduce:

1. find shopee
2. edit 1 s/approved

Expected: If a user wants to edit multiple filtered jobs at a time, it would be much more convenient if editing a job does not reset the filter, i.e. the list is still the filtered list for the user to edit further

[nus-se-bot]

Team's Response

The find command was designed for the user to find and select a particular application. Once the application has been found, the edit command will edit the data of the selected application. If the user wants to edit other applications, they can find then edit again. This does not affect the usability of the app and the user should go through the prescribed process to edit multiple applications in the list.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement: I agree that this feature flaw does not affect the usability of the app, but fixing it would be very beneficial to the target users (who have many job applications and favour CLI apps). Below are my reasonings:

• The use case to edit multiple filtered applications at a time can occur quite frequently for the target user group, because the fact that some applications are filtered at the same time means that they have something in common, e.g. industry, job type, job status, interview date etc. and it's common for the user to want to edit multiple interviews details or job status for a group of applications at the same time.

• The current design creates too much unnecessary hindrance to the user. If the user wants to edit multiple filtered applications, they have to key in the same find command multiple times which is potentially a long command and thus time-consuming. In contrast, if the list stays filtered, the user still has the freedom to go back to the unfiltered list by simply typing the list command which is much more convenient.

Therefore, although the app works without this improvement, in my opinion it is not optimised for CLI usage and creates very noticeable inefficiency in the usage, and thus should be improved.

---