We are currently Auto Transition Listener to transition an issue from "Waiting for Customer" to "Under Investigation". This seems to be working fine. We are also using JIRA Service Desk's SLA functionality. We have an SLA that is set to pause when the status is updated to "Waiting for Customer", then resume when moving back to "Under Investigation". The problem we are having is that when this transition is done automatically via the listener, the SLA does not resume. Is there something we need to do to trigger the SLA to resume?
We have the same problem. Workflow with statuses "Waiting for User", "Waiting for Service Desk" and transition from first to second one. When issue is in the status "Waiting for user" SLA is paused. In case "Waiting for Service Desk" time of SLA is running. If we launch this transition manually, it all works perfect. We have also auto transition listener triggered by user' comment - it works almost good: transition is realized, status changed from "user" to "service desk", as we defined, but SLA is still paused and we don't know why.
SLA field "Pause on (Optional) Time is not counted during" is filled by "Waiting for User" status only. If we recalculate and update SLA manually, time is starting. What we should do more?
JIRA 6.3.8, JIRA Service Desk 2.1.1, JIRA Toolkit Plugin 0.35.11.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
...word of mouth, so by 2016, we were working with several other entities on campus to implement Jira Service Desk . The Atlassian motto of “for every team” has really come true for us in this case. We...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs