Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-3303

Add more customizable SLA time to automation "When" trigger

    XMLWordPrintable

Details

    • 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 Service Desk Cloud. Using JIRA Service Desk Server? See the corresponding suggestion.

      We would like to customize the time entered into the SLA "when" rule beyond the current 60min/30min/breached options.

      The problem is, for P1 or P2 issues, we have an SLA of 15 minutes. With the current automation options, there is no way to alert a user/group of an impending breach. For longer-term SLAs such as MTTR on a lower priority issue, we would want to remind the team longer than 60 minutes in advance.

      Additionally, a "Breach + Time" condition should be available so that we can notify the next level support and/or lead role when a breach has happened beyond a set threshold.

      Attachments

        Issue Links

          duplicates

          Suggestion - JSDCLOUD-12359 Improve SLA Threshold Breached trigger, e.g. ability to define custom durations for SLA triggered events, show only SLA from current project

          • Gathering Interest
          is related to

          Suggestion - JSDSERVER-3303 Add more customizable SLA time to automation "When" trigger

          • Closed

          Activity

            People

              7ad1551c39c0 Benjamin Paton
              e60cee3f62db Matthew Daize
              Votes:
              6 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: