soc-se-bot
commented
4 months ago Team's Response
The User Guide clearly states that The N is the N log from the same meal that the user wishes to delete. Note: N starts with 1. The developer did not adhere to this instruction(did not pay attention to the same meal part), which resulted in the delete function to not work in the way he/she wanted it to.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I think the team has misunderstood the issue. I understand that that index for delete of same meal is based on the nth log from the same meal. The issue is that the feature is flawed because if the user has used the app for a long time, they will have a long list of logs with multiple of the same meal name. If they want to delete something that they have recently added but is a duplicate of past meals, they have to start counting all the way from the top to find the correct nth index for that meal name because there is no indication given for which index it is. This will waste a lof of the users time and is inconvenient for them to use.
Example shown below: I am trying to delete the latest rojak that is logged (index 22 in list) but there is no indication that it is the 11th duplicate of rojak, so i would have to count starting from the top to find the correct index. It does not help that the users have to be sure that the index is correct as deleted logs cannot be recovered if they counter the wrong index accidentally.
If user have a lot of the same meal, and want to delete a specific one , they have to spend a lot of time trying to count the index for the one they want to delete