-
Bug
-
Resolution: Fixed
-
Low
-
14
-
Severity 2 - Major
-
1
-
Issue Summary
When a generic event (system) is configured to trigger a notification for a custom field and said field is moved to trash the configuration persists and this prevents the notification scheme from loading correctly in project settings for any projects that use the scheme.
Steps to Reproduce
- Configure a notification for a custom field using a generic event (system)
- Move custom field to trash
- Attempt to load the notification scheme in any of the projects that use the scheme where the notification is configured
Expected Results
If the field is deleted the configuration should be removed or a warning should be issued to remove the configurations before being able to delete the field
Actual Results
- The field can be removed but the configuration persists and no warning are issued
- The notification scheme doesn't load but the exception is not caught and the page remains in a loading state.
Workaround
Restoring the field or deleting the notification events prior to deleting the field.
Steps detailed in this article.