Using the command deleteA deletes only unarchived tasks. When the archived task is later unarchived, and the label is added back to a different task or contact, the number of contacts/tasks associated with the label will also become incorrect.
To reproduce:
Steps:
Add 2 different tasks using addT.
markL both of the tasks with the same label name. Do this by running markL t/2 l/CS2101 and markL t/2 l/CS2101 if the 2 tasks are the only tasks present.
Archive one of the tasks using archiveT 1.
Run deleteA CS2101, or on the label name used in Step 2.
Run listL and notice that the label is no longer displayed.
Run listAT then unarchiveT 1 to unarchive the previously archived task in Step 3.
Add the same label back to the other task using addL.
Notice that the entry in listL displays the wrong association number.
Expected behaviour:
The expected behaviour is that either unarchived tasks are also deleted or the label list should be updated correctly.
This is a feature that a user will unlikely chance upon, so its severity is Low. However, it can cause inconvenience for the user expecting the label list to be correct.
Description of the bug:
Using the command
deleteA
deletes only unarchived tasks. When the archived task is later unarchived, and the label is added back to a different task or contact, the number of contacts/tasks associated with the label will also become incorrect.To reproduce:
Steps:
addT
.markL
both of the tasks with the same label name. Do this by runningmarkL t/2 l/CS2101
andmarkL t/2 l/CS2101
if the 2 tasks are the only tasks present.archiveT 1
.deleteA CS2101
, or on the label name used in Step 2.listL
and notice that the label is no longer displayed.listAT
thenunarchiveT 1
to unarchive the previously archived task in Step 3.addL
.listL
displays the wrong association number.Expected behaviour:
The expected behaviour is that either unarchived tasks are also deleted or the label list should be updated correctly.
Screenshots/Video:
video:https://raw.githubusercontent.com/seox123/pe/main/files/ddd6e75f-1c58-4d8c-b311-ee7f0b7841da.mp4
Justification:
This is a feature that a user will unlikely chance upon, so its severity is Low. However, it can cause inconvenience for the user expecting the label list to be correct.