Open danbaterisna opened 2 years ago
This was implemented to adhere to tP constraints of improving testability. As such, we are encouraged to not add extra requests to the users to see if they intend to edit the task for an instance or for multiple occurrences.
Team chose [response.Rejected
]
Reason for disagreement: I see how a Y/N prompt can complicate matters with the interface. However, I believe a warning printed after the operation should not significantly complicate the design.
Team chose [severity.VeryLow
]
Originally [severity.Low
]
Reason for disagreement: A very low severity is reserved for purely cosmetic issues, and this is an issue that an affect usability.
Reproduction: With the following save file:
open the application. Then, edit one instance of the recurring task as follows:
edit 2 task 2 [SUBMIT PAPER DRAFT]
Then, edit the recurring task as follows:
edit 1 task3 /repeat
Expected behavior: Task 2 is unchanged, as per the UG.
Actual behavior: Task 2 is unchanged:
Note that Sherpass gives no warning message after editing a single instance of a recurring task, which may affect a user who simply forgot to add the
/repeat
flag.