soc-se-bot
commented
8 months ago Team's Response
Thank you for your response.
Will take note of this, and make the necessary improvements in the future.
However, in our previous tests, we were given the feedback that it would be nicer if the user was given more tries at deletion.
Previously, if user input a random value, the deletion process would stop, and the user would have to initiate it again.
I think this is the primary value we were looking for.
As for your comment on "y", and "n" having no effect, it is without a doubt, they should have not any effect, as it would mean, they might accidentally delete data.
For your suggestion "It would add value if user needs to click "yes" 5 times to successfully delete to prevent accidental deletions," we believe that giving this confirmation prompt, with 5 tries for any accidental input is more than enough.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I still do not see the value in having 5 tries to delete an entry or stop a deletion if all it takes to perform the actual operation is still just one correct "yes" or "no" command. What I mean by "It would add value if user needs to click "yes" 5 times to successfully delete to prevent accidental deletions,", is that usually when multiple tries are introduced for deletion confirmation, they require the user to enter the correct command more than one time to truly confirm that the user wants to delete the data. Typically, this may take the form of deletion confirmation dialogs. However, in this feature, it is not like the user needs to type "yes" 2 or 3 times to confirm the deletion, all I need is to key in a "yes" once to trigger deletion. Hence it was unintuitive to me.
In this view, I can achieve a similar outcome by completely forgoing the 5 tries feature. This can be done with just one try: I will execute delete for a "yes", stop deletion for a "no" and also abort for all other accidental inputs. The team highlights their concern with this is that "if user input a random value, the deletion process would stop, and the user would have to initiate it again". I believe this behaviour would in fact make sense as it would help to protect critical data from any undefined actions. The focus of the X tries feature and its true value shines much brighter if it is used for enforcing data security and protection (like asking for double yes confirmation to avoid accidental deletions) instead of to provide convenience for clumsy typers who type in wrong commands and do not wish to retype a simple "delete x" to restart the process. It is not like "delete x" is a complicated command that would cause great inconvenience to retype. If the documentation is clearer, I believe users will not be making many mistakes with wrong accidental inputs.
Accidental deletions can still happen with this feature. If I misread the index and typed "yes" on my first command, my entry will be deleted! Asking for double "yes" confirmation can potentially catch the issue before it is too late, and that will bring out the true value of having X tries. In summary, feature does not bring much value to the program and easily causes unnecessary confusion.
## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:**  ------ This bug is not just a cosmetic issue, it directly affects usage of the program as there is insufficient documentation on the outputs and rationale behind the feature that can lead to confusion with users on the 5 tries left feature. Such confusion should not be introduced **especially** when it comes to the direct deletion of data as critical wildlife information is at stake here.
After delete there is a feature for 5 tries left to (presumably confirm the delete), but it was not explained in the UG how this exactly works and the rationale behind this feature, and what would be my final result for different replies in the 5 tries. Through trial and error it was discovered that deletion is instantly rejected or accepted after a "no" and "yes" is keyed in, and all other inputs like "y" and "n" do not have any effect and ends up using the retries. So the question is: how does a 5 retries feature add value? It would add value if user needs to click "yes" 5 times to successfully delete to prevent accidental deletions, but here one "yes" anywhere in the 5 tries is all it takes to delete. Why is there a feature that gives users 5 tries to input random values and react instantly to "no" and "yes"?