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

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

    XMLWordPrintable

    Details

    • Feedback Policy:
      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

            Activity

              People

              • Assignee:
                mlassau Mark Lassau (Inactive)
                Reporter:
                scott@atlassian.com Scott Farquhar
              • Votes:
                18 Vote for this issue
                Watchers:
                35 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