• 825
    • 4
    • 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.

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

      Problem Definition

      Currently, SLA goals needs to be predefined and it's static. In some cases, we need to make it flexible.

      Suggested Solution

      Make SLA goals to be dynamic.
      Eg: SLA goal can be set based on a custom date field.

      Why this is important

      • This is needed to make sure the report is accurate
        • Example: SLA is breached before the due date and this is definitely not the right statistics for the high level management
      Original request

      My issue over here is that I have a date type custom field on JSD customer portal. I need to link my SLA with this Date chosen be the customer. For example deadline SLA should be in sync with the date provided by customer, for every request I will be having different deadline, so constant deadline SLA is not making sense to us at present, Is there any way we can achieve this ?

          Form Name

            [JSDCLOUD-1832] Dynamic SLA Goal in JSM

            Cam S added a comment -

            +1

            Cam S added a comment - +1

            You can change the title ctrilha@atlassian.com as much as you want. Nothing will happen My kid is already in school. I don't remember her first steps, but I remember submitting this feature request. 

            Dusan Vuckovic added a comment - You can change the title ctrilha@atlassian.com as much as you want. Nothing will happen My kid is already in school. I don't remember her first steps, but I remember submitting this feature request. 

            +1 (one of the base functions I expect in ITSM tool)

            Pavel Kratky added a comment - +1 (one of the base functions I expect in ITSM tool)

            Hello, I am an ITSM administrator in my organization and I have the need to create SLA with a custom field.

            André Guimarães added a comment - Hello, I am an ITSM administrator in my organization and I have the need to create SLA with a custom field.

            This is a real needed feature, basically i want to use asset cf to trigger the SLA and not making a lot of working around with WF and Automation to set up this. 

            Danilo Gomes added a comment - This is a real needed feature, basically i want to use asset cf to trigger the SLA and not making a lot of working around with WF and Automation to set up this. 

            Waiting for this improvement. We want to use the Due date as the SLA breach time.

            Erki Tammik added a comment - Waiting for this improvement. We want to use the Due date as the SLA breach time.

            Come on already guys. We are begging here for 8 years. Windows was built in less time 

            Dusan Vuckovic added a comment - Come on already guys. We are begging here for 8 years. Windows was built in less time 

            Hamzah Mohamed added a comment - - edited

            This feature would be extremely helpful, but it doesn't need a full feature lifecycle to fulfil most problem scenarios.

             

            In my opinion, you could go a long way with just enabling the editing of the "breachTime" entry, so that we could use Jira Automations to edit it – even as a "dark feature" that can be toggled on or off. Then we could use Smart Values and other types of logic in Automations to be able to adjust when the breachTime reach should happen.

             

            Currently, we would have to rely on an entirely separate plugin, that overhauls the entire way users interact with SLAs, to just get a bit of flexibility with SLA.

             

            Hamzah Mohamed added a comment - - edited This feature would be extremely helpful, but it doesn't need a full feature lifecycle to fulfil most problem scenarios.   In my opinion, you could go a long way with just enabling the editing of the "breachTime" entry, so that we could use Jira Automations to edit it – even as a "dark feature" that can be toggled on or off. Then we could use Smart Values and other types of logic in Automations to be able to adjust when the breachTime reach should happen.   Currently, we would have to rely on an entirely separate plugin, that overhauls the entire way users interact with SLAs, to just get a bit of flexibility with SLA.  

            Still praying for this to be included in Jira SLA: goal duration to be taken from custom field.

            Projects with multiple calendars and varied goals and many different SLAs are not possible to work with Jira SLA module. We are at the mercy of external SLA add-ons that offer this feature but in exchange: are messy, bad QA for every push to live, work fine one day are are broken the next.

            Please!

            Leonard Hussey added a comment - Still praying for this to be included in Jira SLA: goal duration to be taken from custom field. Projects with multiple calendars and varied goals and many different SLAs are not possible to work with Jira SLA module. We are at the mercy of external SLA add-ons that offer this feature but in exchange: are messy, bad QA for every push to live, work fine one day are are broken the next. Please!

            Karol Wnuk added a comment - - edited

            It totally makes sense. Use case:

            • HR team sends onboarding/offboarding request. The due date should be calculated based on the joiner/leaver start/last day that is submitted in the form.

            Karol Wnuk added a comment - - edited It totally makes sense. Use case: HR team sends onboarding/offboarding request. The due date should be calculated based on the joiner/leaver start/last day that is submitted in the form.

              8a3861d8a88c Manas Shukla
              5a24e453eb10 Mahesh Dubey
              Votes:
              386 Vote for this issue
              Watchers:
              158 Start watching this issue

                Created:
                Updated: