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

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

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • SLA
    • None
    • 0
    • 3
    • 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.

      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.

          Form Name

            [JSDSERVER-494] Service needs an SLA configuration audit trail and a issue history of the SLA config that was in play

            Alex Cooksey made changes -
            Resolution Original: Won't Do [ 10000 ] New: Low Engagement [ 10300 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Charlie Marriott made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            SET Analytics Bot made changes -
            UIS Original: 3 New: 0
            Arnaud Errede (Inactive) made changes -
            Description Original: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-494].
              {panel}

            Today when you change SAL 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.             		New: {panel:bgColor=#e7f4fa}
            *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-494].
            {panel}
            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.
            SET Analytics Bot made changes -
            UIS Original: 2 New: 3
            SET Analytics Bot made changes -
            UIS Original: 3 New: 2
            SET Analytics Bot made changes -
            UIS Original: 2 New: 3
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3012767 ] New: JAC Suggestion Workflow 3 [ 3651367 ]
            SET Analytics Bot made changes -
            UIS Original: 3 New: 2
            SET Analytics Bot made changes -
            UIS Original: 2 New: 3

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

                Created:
                Updated:
                Resolved: