Editing a task using the edit command will result in the Task List not working

[AaronCQL]

Steps to reproduce:

1. Assume we are using the sample data
2. Execute list module
3. Notice that CS3230 is the first item listed:
4. Execute edit 1 m/cs3230 (notice the small caps in "cs")
5. Resulting list is shown:
6. Note that the CS3230 tasks completely disappears from the whole task list even when scrolled to the bottom

[nus-pe-bot]

Team's Response

Bug issue with display. Task will reappear if list is refreshed. The app should not be considered unusable as other operations can continue to proceed.

Items for the Tester to Verify

:question: Issue severity

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

• [x] I disagree

Reason for disagreement: I agree that the app can be used if the the list is refreshed. However, this requires the user to know about this bug in the first place, and to also know how to refresh the list. For example, to refresh the list, a user would have to execute list first, then list module once more. Simply executing list module after this bug happens will not refresh the list.

Moreover, without refreshing the list, most other operations cannot continue to proceed. All the commands that rely on the indices of the tasks will not be executed correctly as the indices displayed are wrong. For instance, let's start off with the "bugged" list as shown in step 5 of the original bug report (where the CS3230 tasks completely disappear):

1. Now, say you want to execute a command that requires the index of the tasks. For example, let's try to edit the description of EC1103 to something else. In this screenshot, the index of this task is clearly 5:
2. However, executing edit 5 d/Changed Description will result in this: Notice that the description that changed is actually the task with index 7, not 5.

Likewise, all the commands in this app that rely on the indices will not produce the expected output. For example, the commands edit, done, delete, reminder, delrem, and start will all not produce the expected result since the task actually executed on does not correspond to the task the user meant.

As such, I believe this is in line with the description of severity.High, where it "causes major problems for users", since a majority of commands in this app requires the index of the tasks. Users are only able to continue using the product and view the missing tasks by refreshing the list, which is not something trivial to do.

---