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.

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

            Charlie Marriott added a comment -
            Atlassian Update – 19 Feb 2021

            Hi,

            Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

            Regards,

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 19 Feb 2021 Hi, Thank you for raising and watching this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Jira Service Management, Server & Data Center

            Michal Orzechowski (Inactive) added a comment -

            There is an API (experimental) to add simple information about what has changed, but currently there is nothing to support JSON or BLOB types that has changed.

            Michal Orzechowski (Inactive) added a comment - There is an API (experimental) to add simple information about what has changed, but currently there is nothing to support JSON or BLOB types that has changed.

            ɹǝʞɐq pɐɹq added a comment -

            Yes but I am currently unsure about the "extensibility" of it. eg can it take arbitrary events or does it need to be extended to understand new events.

            morzechowski might know more

            ɹǝʞɐq pɐɹq added a comment - Yes but I am currently unsure about the "extensibility" of it. eg can it take arbitrary events or does it need to be extended to understand new events. morzechowski might know more

            Justus Pendleton (Inactive) added a comment -

            bbaker, is there an Audit API we can use for this?

            Justus Pendleton (Inactive) added a comment - bbaker , is there an Audit API we can use for this?

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

                Created:
                Updated:
                Resolved: