search

uggi121 / pe

0 stars 0 forks source link

Remind Functionality Bug #7

Open uggi121 opened 4 years ago

uggi121 commented 4 years ago

The remind feature for "flashcards" doesn't work for new flashcards.

Upon addition of a new flash-card, the remind feature is supposed to prompt the user to revise that particular flash-card. However, this isn't reflected.

image.png

image.png

Remind still shows nothing to revise, in spite of the latest addition. This is a deviation from the behaviour specified in the UG

image.png

nus-pe-bot commented 4 years ago

Team's Response

This bug is rejected because this is completely expected behaviour. As stated in the user guide, the point of the remind command is to use it every day to check which flashcards ought to be revised tha day (which StudyBuddyPro automatically plans out for the user). The reason why a newly added flashcard is not due for revision the day it is added is obvious - the flashcard was just added and by nature that means it was just revised before being added as the user had to type in the question and answer. Also, the bug report states that "Remind still shows nothing to revise, in spite of the latest addition. This is a deviation from the behaviour specified in the UG", but it is not stated anywhere in the UG how the remind command will work specifically after a new flashcard is added. In fact, the UG clearly states "StudyBuddyPro automatically sets the date the flashcard should next be viewed at for optimal learning.", and the new flashcard not showing up is simply because its date is not due yet. Finally, there is a clear section on manual testing the remind command in the DG which involves simply changing the system date which the tester could have used, but it seems the tester did not read that section and which is why has failed to test the remind command effectively.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: The behaviour is extremely ambiguous and opaque from a user and a developer perspective. Even if this is the expected functionality, the documentation is severely lacking and WILL cause many users inconvenience. Thus, if not a functionality bug, this issue should qualify as a documentation bug.

:question: Issue severity

Team chose [severity.Low]. Originally [severity.Medium].

Reason for disagreement: [replace this with your reason]