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

Ability to define custom durations for SLA triggered events for automation rules

    • 14
    • 26
    • 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 Management Data Center. Using Jira Service Management Cloud? See the corresponding suggestion.

      Problem Definition

      When creating an automation rules in Service desk project, there is only 3 option for SLA time remaining event:

      • Due soon (60m remaining)
      • At risk (30m remaining)
      • Breached

      Suggested Solution

      Need an ability to accept user input values for the condition.

      Workaround

      Similar feature can be achieved by creating an issue filter and then subscribe to the filter to get email notification. The JQL will be something like:

      project = DESK and "Time to resolution" <= remaining("15m") and "Time to resolution" != breached()
      

      Note: Please change the values accordingly to your environment.
      This query will return issues in project "DESK" that it's SLA haven't breached and the remaining SLA is 15 minutes or less.

      And then, for the filter subscription, you can choose to send an email every 15 minutes or use "Advanced scheduling ('cron')" for more detailed intervals; Receiving Search Results via Email.

            [JSDSERVER-2003] Ability to define custom durations for SLA triggered events for automation rules

            Sam Young added a comment -

            +1

            Sam Young added a comment - +1

            Any update on this? Most of the client is looking for this functionality.

            Nico Ocampo added a comment - Any update on this? Most of the client is looking for this functionality.

            James M added a comment -

            This would be extremely helpful from a user standpoint as we would like to set custom SLAs not using the 2 hour 30 minute and breached mark.  Workaround requires more users to subscribe to the subscription feature.  We would rather be able setup this feature using the automation to only those who are agents up front.  

            James M added a comment - This would be extremely helpful from a user standpoint as we would like to set custom SLAs not using the 2 hour 30 minute and breached mark.  Workaround requires more users to subscribe to the subscription feature.  We would rather be able setup this feature using the automation to only those who are agents up front.  

            This would be very helpful, any updates?

            Israel Chavez added a comment - This would be very helpful, any updates?

            Would indeed be very nice to simplify our logic.

            Anton Danielsson added a comment - Would indeed be very nice to simplify our logic.

            This would be very useful, very surprising it isn't already in JIRA

            Eoin Boylan added a comment - This would be very useful, very surprising it isn't already in JIRA

            Love the idea of this feature- would be so useful for support/success teams to have that pre-deadline warning.

            Kristen Lindorf added a comment - Love the idea of this feature- would be so useful for support/success teams to have that pre-deadline warning.

            kfraaken added a comment -

            This feature would be useful.

            kfraaken added a comment - This feature would be useful.

            Riduculous this isn't a feature already. I should be able to set any hour interval I would like. Also triggering an event off the due date should be possible also. (e.g. If there are n hours/days left till the due date then do xyz)

            nick skinner added a comment - Riduculous this isn't a feature already. I should be able to set any hour interval I would like. Also triggering an event off the due date should be possible also. (e.g. If there are n hours/days left till the due date then do xyz)

            Anna Moran added a comment -

            We would love this feature please

            Anna Moran added a comment - We would love this feature please

            mluderich added a comment -

            We absolutely need this feature. As is, this is helpful to alert people when we breach reaction times, but our SLAs quite often have solution deadlines that last up to a few days. The current time options just don't cut it there.  

            mluderich added a comment - We absolutely need this feature. As is, this is helpful to alert people when we breach reaction times, but our SLAs quite often have solution deadlines that last up to a few days. The current time options just don't cut it there.  

            Would be useful, we need to warn the reporters before closing the ticket, and most of the times 1 hour isn't enough.

            João Oca added a comment - Would be useful, we need to warn the reporters before closing the ticket, and most of the times 1 hour isn't enough.

            James H added a comment -

            Definitely a must!  I need the ability to alert both prior to breach, at breach, and for certain hours beyond breach.  

            James H added a comment - Definitely a must!  I need the ability to alert both prior to breach, at breach, and for certain hours beyond breach.  

            We are also using SLA when customer response is needed, so also without workaround.

            Please try to fix this!

            Anders Fältros added a comment - We are also using SLA when customer response is needed, so also without workaround. Please try to fix this!

            We use it for SLA regarding missing customer feedback, so the workaround is no solution for us.

            Do we really need also a 3rd party plugin for that, because we cant specify the exact time in minutes?

             

            Walter Haas added a comment - We use it for SLA regarding missing customer feedback, so the workaround is no solution for us. Do we really need also a 3rd party plugin for that, because we cant specify the exact time in minutes?  

            A normal use case is to use the SLA counters in combination with automation rules to send warning notifications to customer after for example 10 days in waiting for customer and auto-resolving issue after 15 days in Waiting for customer. 

            Without possiblitiy to customize the number of hours/minutes in the automation breached rule, it is necessary to add two SLA:s for those two automation rules 

            If automation rule could be customized by setting a number of hours, there will only be need for one single Waiting for customer SLA rule. 

             

            Björn Gullander added a comment - A normal use case is to use the SLA counters in combination with automation rules to send warning notifications to customer after for example 10 days in waiting for customer and auto-resolving issue after 15 days in Waiting for customer.  Without possiblitiy to customize the number of hours/minutes in the automation breached rule, it is necessary to add two SLA:s for those two automation rules  If automation rule could be customized by setting a number of hours, there will only be need for one single Waiting for customer SLA rule.   

            Would really love to see this feature. As stated above, sometimes an SLA is short enough to merit the option of providing a custom alert scheme. 

             

            For instance, we have a one hour response on all highest priority items, and I want to notify the entire team 10-15 minutes ahead of the breach, but that's not possible without really getting involved with filter subscriptions. Total pain for what seems like a simple-enough change. 

            Meg Holbrook added a comment - Would really love to see this feature. As stated above, sometimes an SLA is short enough to merit the option of providing a custom alert scheme.    For instance, we have a one hour response on all highest priority items, and I want to notify the entire team 10-15 minutes ahead of the breach, but that's not possible without really getting involved with filter subscriptions. Total pain for what seems like a simple-enough change. 

            Agreed, this would be a huge benefit. I was just looking for this feature now as it is a requirement for our teams.

            stefan kolesnikowicz added a comment - Agreed, this would be a huge benefit. I was just looking for this feature now as it is a requirement for our teams.

            robertno added a comment -

            Absolutely vital considering the functionality is already there to fire the notification. Even if the ability to set the custom event could only be restricted to a "Due soon" or "At risk" queue/time within the associated JSD queue - but certainly the option to alter the SLA time remaining would move this feature from nice to hugely beneficial.

            robertno added a comment - Absolutely vital considering the functionality is already there to fire the notification. Even if the ability to set the custom event could only be restricted to a "Due soon" or "At risk" queue/time within the associated JSD queue - but certainly the option to alter the SLA time remaining would move this feature from nice to hugely beneficial.

            robk added a comment -

            This is vital. Imagine for example, a 30 minute SLA goal. Naturally, an alert at 30m remaining or elapsed is of no use at all.

            robk added a comment - This is vital. Imagine for example, a 30 minute SLA goal. Naturally, an alert at 30m remaining or elapsed is of no use at all.

              Unassigned Unassigned
              mmuthusamy Moga
              Votes:
              142 Vote for this issue
              Watchers:
              69 Start watching this issue

                Created:
                Updated: