-
Suggestion
-
Resolution: Fixed
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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
-
JRASERVER-30293 Duplicating issue when replying to e-mail
- Closed
-
JRASERVER-31125 Email threading can break due to subtly different In-Reply-To ID values
- Closed
-
JRASERVER-31365 Outgoing emails not threading in Outlook when connected to Exchange Server
- Long Term Backlog
- incorporates
-
JRASERVER-4298 Notification message cleanup service
- Closed
- relates to
-
JRASERVER-11725 Exporting data from a JIRA instance with a lot records in the notificationinstance table causes an OutOfMemoryException
- Closed
-
JRASERVER-29761 Outgoing emails not threading in Outlook
- Closed
-
JRACLOUD-9979 NotificationInstance's should have a creation date, and a service to clean them up
- Closed
-
JRASERVER-11181 Comment creation from emails using the mail service should also check the references header
- Closed
-
JRASERVER-30824 Use 'References:' field in Jira Mail
- Closed
-
JRASERVER-44418 Periodically clean up the notificationinstance table
- Gathering Interest
- was cloned as
-
JRADEV-14311 Loading...