Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-9979

NotificationInstance's should have a creation date, and a service to clean them up

    XMLWordPrintable

Details

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      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.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-30293 Duplicating issue when replying to e-mail

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-31125 Email threading can break due to subtly different In-Reply-To ID values

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-31365 Outgoing emails not threading in Outlook when connected to Exchange Server

          • High - High priority issues
          • Long Term Backlog
          incorporates

          Suggestion - JRASERVER-4298 Notification message cleanup service

          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-11725 Exporting data from a JIRA instance with a lot records in the notificationinstance table causes an OutOfMemoryException

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-29761 Outgoing emails not threading in Outlook

          • Low - Low priority issues
          • Closed

          Suggestion - JRACLOUD-9979 NotificationInstance's should have a creation date, and a service to clean them up

          • Closed

          Suggestion - JRASERVER-11181 Comment creation from emails using the mail service should also check the references header

          • Closed

          Suggestion - JRASERVER-30824 Use 'References:' field in Jira Mail

          • Closed

          Suggestion - JRASERVER-44418 Periodically clean up the notificationinstance table

          • Gathering Interest
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          was cloned as

          JRADEV-14311 Loading...

          Activity

            People

              mlassau Mark Lassau (Inactive)
              scott@atlassian.com Scott Farquhar
              Votes:
              18 Vote for this issue
              Watchers:
              34 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 8h
                  8h
                  Remaining:
                  Remaining Estimate - 8h
                  8h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified