Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-5266

Provide clean up schedule job for AO_54307E_SLAAUDITLOGDATA

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 3.7.0
    • None
    • None
    • We collect Jira Service Desk 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.

      Problem Definition

      We currently have an SLA Audit Log introduced since JSD 3.4.1 for troubleshooting SLA. Although this feature isn't designed for end users and should require no maintenance by Service Desk admins, there is no automatic house-cleaning provided for the data it accumulates in AO_54307E_SLAAUDITLOGDATA and AO_54307E_SLAAUDITLOG tables.

      On a heavily used JSD instance this tables could swell up to millions of records within a few months.

      Suggested Solution

      Provide a scheduled job to clean up the AO_54307E_SLAAUDITLOGDATA and AO_54307E_SLAAUDITLOG tables, or allow some configurable clean up schedule.

            [JSDSERVER-5266] Provide clean up schedule job for AO_54307E_SLAAUDITLOGDATA

            Matthew McMahon (Inactive) added a comment -

            A cleanup job has been added to 3.7.0

            This will run once a day and look for the follow data to delete:

            • Issues with no Audit events in last 30 days (this value is configurable as global property in database `sd.sla.audit.log.cleanup.days`)
            • Of those potential audit events to cleanup, ensure that the Issue has no Ongoing SLA Cycles
            • If no events in 30 days and no Ongoing SLA Cycles, then delete the Audit Data associated with that issue

            Matthew McMahon (Inactive) added a comment - A cleanup job has been added to 3.7.0 This will run once a day and look for the follow data to delete: Issues with no Audit events in last 30 days (this value is configurable as global property in database `sd.sla.audit.log.cleanup.days`) Of those potential audit events to cleanup, ensure that the Issue has no Ongoing SLA Cycles If no events in 30 days and no Ongoing SLA Cycles, then delete the Audit Data associated with that issue

              mmcmahon Matthew McMahon (Inactive)
              takindele Taiwo Akindele (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: