...
| Button handy |
|---|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
| Button handy |
|---|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
This page is about Time to SLA for Jira Cloud. Using Jira ServerOn-Prem? Click the Server On-Prem button above. |
Rest APIs can help you edit and view your SLA data.
...
To use these APIs, you need a JWT token for authorization.
To create a new token:
...
Navigate to Settings > API Token
...
.
...
Click New Token to create a token.
...
...
Name your token, select when it'll expire, or check the Never expire box to make sure the token doesn’t expire in a certain time period, and how much access it will have. Click Save.
...
| Note |
|---|
For security reasons, we do not recommend generating tokens that never expire. Please be aware that if this token is somehow exposed, you will need to delete it manually, as it will not expire automatically. |
...
The JWT Token will appear. Save it by clicking the icon shown below. Keep in mind that you won’t be able to access this code after closing the pop-up.
...
...
Click Cancel after copying the token, and the token will appear on the main page.
...
Replace {{jwtToken}} in the header with your token.
| Note |
|---|
Important note: Keep in mind that your JWT must have permission and access to use these APIs. For example, even if your JWT token has access to SLA APIs, you cannot utilize them if you do not have authority to view SLA configurations or administer SLAs. |
...
We’ll give you an example of giving JWT authorization using Postman. 1.
...
Click Run in Postman > Postman for Web.
...
...
On the Postman main page, click Workspaces > My Workspaces.
...
...
Click ➕ to add a new permission.
...
...
Here, to give authorization, first copy and paste the link of the token you’ve chosen from here.
| Note |
|---|
Please don't change the link to reflect your own instance. You can only change the parameters (i.e., issue ID, SLA ID, etc.). |
...
Click Headers.
...
Under KEY, write Authorization.
...
Under Value, write “Bearer (paste the token you’ve created and copied)”
...
Click Send.
...
...
Tada! You’ve successfully given the JWT authorization.
If you don’t know how to get the issue-id on Cloud, you should know there are many ways you can do that. One way is that the issue ID will appear on the result of the below call, like this: BASE_URL/rest/api/3/issue/{issueKey}
...
For better comprehension, we included definitions for some values of an example response below.
Example Response for “Get Issue SLA of Issue” | Meaning |
|---|---|
| This is the SLA’s goal. |
| This is also related to the the SLA goal. We keep this value in milliseconds. |
| If the SLA has started, this will show the start date. We keep this value in unix timestamp. If you want to convert it to human readable form date, you can use a converter. |
| If the SLA has finished, this will show the end date. We keep this value in unix timestamp. If you want to convert it to human readable form date, you can use a converter. |
| This is the Target Date. We keep this value in unix timestamp. If you want to convert it to human readable form date, you can use a converter. |
| Elapsed time is the total time the SLA has taken until this time. |
| The time left until the SLA breaches. |
| The time that has passed since the SLA was breached. |
| The lenght of time that SLA has been paused. |
| This value is the same with |
{{baseUrl}}/rest/tts-api/1.0/sla-history-new?issueId=10400&slaId=339
. |
🖇️ Related Articles
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||