Open shaunlxw opened 4 months ago
Severity VeryLow
as it does not affect normal operations at all. UG should have been phrased better to accurately describe the behaviour of the redo
command.
Team chose [severity.VeryLow
]
Originally [severity.Medium
]
Reason for disagreement: Not just purely cosmetic, as it can affect the user's usage of the app in the scenario described below.
Steps:
add n/John m/A1234567X tl/thejohn e/john@example.com
undo
list
(to check the results of the undo, since undo does not change the view to show the whole unfiltered view)redo
since it isn't immediately after an undo
command. He will then need to retype add n/John m/A1234567X tl/thejohn e/john@example.com
again, decreasing the efficiency of the use of the app.In hindsight, it might be possible to downgrade the severity to low. However, to note that medium is still possible as it should be quite common for user to call list
after undo
to check the results of the undo
as stated in step 3 above, causing user to think they cannot use the redo
command after list
, and have to retype the whole command again to redo the action.
UG mentions that "Redo command must be issued immediately after an undo command". This is not accurate from testing as the below is allowed.
Steps:
Might mislead user that they cannot redo their command that changed data after doing a list command