Uploaded image for project: 'Jira Cloud (including JIRA Core)'
  1. Jira Cloud (including JIRA Core)
  2. JRACLOUD-9979

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

    XMLWordPrintable

    Details

    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

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