Service needs an SLA configuration audit trail and a issue history of the SLA config that was in play

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Low Engagement
    • None
    • Component/s: SLA
    • None
    • 0
    • 3

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      Today when you change SLA configuration it can have dramatic effects about what SLA's are running or not.

      For general support reasons we should have a "history audit" of the SLA configurations that are in place at a given point in time.

      This would be all the configuration and when it applied.

      This could then be used by admins and atlassian support to debug how the configuration has changed and how it should be applied to current and past issues.

      Also we could have an issue history record that says WHEN an given SLA configuration was being applied to an issue and when new ones are overriding it (eg when we drop an SLA timer because of a config change)

      This would also help for support reasons.

            Assignee:
            Unassigned
            Reporter:
            ɹǝʞɐq pɐɹq
            Votes:
            7 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: