I writing a small powershell script to create a workaround for our SLA problem (we are already in contact with Atlassian Support to fix the root cause). The problem is, that the workaround explained here https://confluence.atlassian.com/jirakb/missing-sla-data-in-jira-servicedesk-828790603.html, works fine except, that someone manually have to do the following step:
"Navigate to the Service Desk Project Administration and click on the " Update" icon under the SLAs section."
I was wondering, if someone knows an API way to do this particular step (unfortunately I couldn't find one)
You can open the browser you use for browsing your Jira site and go to developer tools. Then you push the update button and check what rest call was used on the Network tab of your developer tools window.
Anyway it will be internal REST API which can be changed by Atlassian any time.
For example, in my version of Service Desk it is POST /rest/servicedesk/1/servicedesk/projectkey/sla/consistency.
If you don't have a Rest client, you can also proceed with that within a cURL command as my example below where I'm reconstructing the SLA of the issue "DEVSPT-1453"
curl -D- -u username:password -X POST -H "Content-Type: application/json" --data '["DEVSPT-1453"]' "http://jira_server/rest/servicedesk/1/servicedesk/sla/admin/task/destructive/reconstruct"
Just ensure to rename the username/password in order to authenticate correctly and also jira_server according to your instance's FQDN.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
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