nus-pe-bot
commented
4 years ago Team's Response
It is hard for us to allow the user to edit fields before finishing the entire prompt sequence (which is not that long, anyway). Constantly prompting the user for confirmation of a field would degrade the user experience.
Furthermore, edit is not an essential functionality. Flashcards are expected to store bite-sized pieces of information, and it should not be too much trouble to delete one and remake it. In fact, the effort taken to edit one flashcard (select the flashcard, then select the field, then change the field) is almost equivalent to creating a new flashcard by copy-pasting the previous fields. That is, unless the flashcard contains a very large number of details, which is likely to be the exception rather than the norm.
Hence, we believe the existing flashcard operations are sufficient to offer a complete experience.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Well, firstly it brings convenience to me as a user, thus it was raised as a feature flaw rather than a functionality bug. My intention was that the product should at least allow the user to exit from the prompt sequence if he/she realised an error in an earlier attribute. Having to go through the whole sequence, knowing you made a mistake (and ensuring the formatting is still correct such as the dates), will definitely be cumbersome as a user, since I know I will be deleting it and remaking it again.
Secondly, it will actually be OK to delete and remake a card IF your application used a single line input to create a card, instead of a multi-layered prompt sequence. For the former, I can simply copy and paste the line, and thereafter change the particular attribute. But for the latter, I have to copy attribute by attribute, which takes much more time. Having an edit feature will therefore be more practical in your product's case, with so many attributes involved. Editing can be targeted to specfic fields, which saves time. No edit command would amplify the first issue, which is that the user will now definitely have to fill in dummy data for subsequent fields if he/she made an earlier mistake, which is not user-friendly and practical at all.
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [x] I disagree
Reason for disagreement: As stated in the Issue Response, it becomes rather cumbersome as a user who made a mistake (perhaps a small typo) in an attribute, to have to delete and remake the entire card again from scratch. This will cause ocassional problems for me as a user.
As the entering of history card is layered by individual prompts, it is not possible to change an earlier attribute after typing it and realising it was wrong.
For example, in the image above, if the death date was entered wrongly, I cannot change it until I finish the entire prompt sequence. Furthermore, there is no edit command to change, so the user has to delete and remake a new card.