-
Bug Report
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
2
-
M
-
3 - Expected
Context:
When creating an alert for a duration report and then editing this report to be a number report (and vice versa), the alert continues to exist and changes target value. This could be confusing. Instead, we should prompt the user to delete the alert, similar to the behaviour implemented in OPT-5052.
Steps to reproduce:
- Create and save a duration report inside a collection
- Create and save an alert for this report, for example with target duration 100 days
- Go back to the report and change the report setup to be a number report (leave everything else unchanged)
- Save the report
- Go back to the alert section
Observed Behaviour:
The alert still exists and now has a target value of 8,640,000,000.
Expected behaviour:
In step 4, the user should be alerted that saving the report will also delete the alert. Upon confirming, the report is saved and the alert deleted.
Note the same behaviour also exists the other way around (create number report and edit it to be a duration report after alert creation).
AT:
- Return conflict response when saving a report that was previously a duration/number and has been changed to be a number/duration report and has an alert associated with it
- Delete the associated Alerts on confirmation (force save)