-
Suggestion
-
Resolution: Fixed
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Currently the support system has 486k notificationinstances in JIRA's support system. There is no way currently to clean them up easily.
If we can add a 'created' column to the notificationinstance table, then we can periodically remove ones that aren't relevant anymore.
For the old ones, can we have an upgrade task that sets the created date to be either the date of upgrade, or the date of update of the issue?
Notes
Please refer to Preparing for JIRA 5.2 for a thorough explanation about how the changes within this improvement request affect JIRA and the way it now handles mail.
- causes
-
JRACLOUD-30293 Duplicating issue when replying to e-mail
- Closed
-
JRACLOUD-31365 Outgoing emails not threading in Outlook when connected to Exchange Server
- Gathering Impact
- incorporates
-
JRACLOUD-4298 Notification message cleanup service
- Closed
- is related to
-
JRASERVER-9979 NotificationInstance's should have a creation date, and a service to clean them up
- Closed
- relates to
-
JRACLOUD-29761 Outgoing emails not threading in Outlook
- Closed
-
JRACLOUD-11181 Comment creation from emails using the mail service should also check the references header
- Closed
-
JRACLOUD-30824 Use 'References:' field in Jira Mail
- Closed
-
JRACLOUD-44418 Periodically clean up the notificationinstance table
- Closed