ryukanjit / pe

0 stars 0 forks source link

Adding/Editing new CCA to match the CCA in reminder causes the reminders and CCA to be linked but not deleted when new CCA is deleted #4

Open ryukanjit opened 2 years ago

ryukanjit commented 2 years ago

Continuing from the feature flaw I proposed where the reminders are not deleted along with the CCA, if new CCA is added with the same name or later edit to fit the ones in the existing reminders, the reminders are now 'linked' with that CCA (which is good) but when the CCA is deleted the reminders are still there.

Consider the following scenario:

New CCA is added with reminders still remaining after deletion: Screen Shot 2564-11-12 at 16.45.22.png

The name of CCA is changed to that of the CCAs that exist in reminder: Screen Shot 2564-11-12 at 16.45.53.png

Every CCAs are deleted: The name of the CCA is changed so do the ones in the reminder despite them being conceptually^ different CCA by the time the CCA is added: Screen Shot 2564-11-12 at 16.47.37.png

Screen Shot 2564-11-12 at 16.54.57.png

^conceptually as in it was not intended to be the same CCA in the first place but the name is changed to be the same intentionally to create the bug

PS: surprisingly the other reminder is now actually deleted with the CCA being deleted but not for the ones that actually still remain in the reminder, it is surprisingly still there. The team has made effort to deal with this bug before but further investigation is required after the PE since the bug still remains in my case.

nus-pe-bot commented 2 years ago

Team's Response

As "Deleting CCA does not delete the reminder(s) associated with that CCA #4566" cannot be reproduced, my team cannot recreate this bug either. Thank you.

Items for the Tester to Verify

:question: Issue response

Team chose [response.CannotReproduce]

Reason for disagreement: On second observation, this bug report actually consists of 2 bugs

Please follow these steps to reproduce the bug.

**Bug 1: The name of the undeleted reminder is changed when a new CCA's name is changed to match the one that it fits (FeatureFlaw - the unassociated CCA should not be able to relink with the existing undeleted reminder) (severity.Medium - since it is occasional: the user can expect to reproduce this bug not rarely)

  1. Create a CCA with reminder(s) associated with it Screen Shot 2564-11-16 at 20.11.55.png
  2. Create another CCA Screen Shot 2564-11-16 at 20.12.23.png
  3. Change the name(s) of of the reminder(s) associated with the first CCA Screen Shot 2564-11-16 at 20.14.10.png Screen Shot 2564-11-16 at 20.15.53.png
  4. Delete the first CCA Screen Shot 2564-11-16 at 20.17.43.png
  5. Change the name of the remaining CCA to match the one in the undeleted reminders Screen Shot 2564-11-16 at 20.18.17.png
  6. Change the name of the newly edited CCA - the reminders' CCA tag are changed along with the new and unrelated CCA (bug 1) Screen Shot 2564-11-16 at 20.18.37.png **Bug 2: The newly linked CCA when deleted would not allow the new reminders associated with it to be deleted
  7. Delete the CCA - this bug is duplication of the first bug where the edited reminders are not deleted along with the CCA (bug 2) Screen Shot 2564-11-16 at 20.19.00.png

:question: Issue severity

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

Reason for disagreement: I would like to change the severity from severity.High to severity.Medium but definitely not severity.Low like the team suggests.

As explained above, I would like to re-report this as a FeatureFlaw instead of functionality bug. This arise from the bug when the edited reminder is not deleted along with the CCA so I want to make it on the same level as that bug (a feature flaw that is a result of a functionality bug).

Since the user can occasionally edit the CCA by changing its name, and if the user happen to change the name to fit the one in the undeleted reminder, this would prove to be an occasional feature flaw since the CCA and reminders are not meant to be associated with each other.

associated - meant for each other