REST Services
This page is about Time to SLA for Jira On-Prem. Using Jira Cloud? Click the Cloud button above.
Calendar Rest API
Next-Gen SLA Rest API
Additional Time to SLA Rest API
Saving SLA definition
Method | POST |
---|---|
URL | /rest/tts-api/latest/sla |
Sample Result |
---|
|
Origin and target dates are custom fields
 |
---|
|
Possible Responses |
---|
|
With negotiation time
 |
---|
|
Possible Responses |
---|
|
With pauses
POST Data |
|
Possible Responses |
---|
|
Bulk saving SLA definitions
Method | POST |
---|---|
URL | /rest/tts-api/latest/sla/bulk |
Sample Result |
---|
|
An SLA with negotiation time and another one with the custom origin and target datesÂ
POST Data |
---|
|
Possible Responses |
---|
|
Showing SLA definition
Method | GET |
---|---|
URL | /rest/tts-api/latest/sla/{slaId} |
Possible Responses |
---|
|
Searching SLA definition
Method | GET |
---|---|
URL | /rest/tts-api/latest/sla/search |
Identifiers for search operation | |
---|---|
-description | Example description=Urgent |
-workflowName | Example workflowName=TTS Project Workflow |
-priorityId | Example priorityId=1 |
-originStatusId | Example originStatusId=3 |
-targetStatusId | Example targetStatusId=5 |
-slaStartDateField | Example slaStartDateField=1 |
-slaEndDateField | Example slaEndDateField=5 |
-multipleTransition | Example multipleTransition=true |
-onlyFirstExecution | Example onlyFirstExecution=false |
-slaValueAsTimeString | Example slaValueAsTimeString=20m |
-slaNegotiationDateFieldId | Example slaNegotiationDateFieldId=11000 |
-slaNegotiationDateIssueFieldKey | Example slaNegotiationDateIssueFieldKey=duedate |
-workingTimeId | Example workingTimeId=3 |
-jqlString | Example jqlString=issuetype = Improvement |
Responses for: /rest/tts-api/latest/sla/search |
---|
|
Responses for: /rest/tts-api/latest/sla/search?description=Urgent |
---|
|
Responses for: /rest/tts-api/latest/sla/search?description=Urgent&slaValueAsTimeString=20m |
---|
|
Listing all SLA definitions
Method | GET |
---|---|
URL | /rest/tts-api/latest/sla/allSlas |
Possible Response |
---|
|
Updating SLA definition
Method | POST |
---|---|
URL | /rest/tts-api/latest/sla |
POST Data |
---|
|
Possible Responses |
---|
|
Updating with Pauses |
---|
|
Possible Responses |
---|
|
Deleting SLA definition
Method | DELETE |
---|---|
URL | /rest/tts-api/latest/sla/{slaId} |
Possible Responses |
---|
|
Get SLA details for an issue
Method | GET |
---|---|
URL | /rest/tts-api/1.0/sla/issue/{issue-key} |
Possible query parameters | |
---|---|
-slaId | Example slaId=26 |
Error Response |
---|
|
SLA ID is given |
---|
|
No SLA ID is given |
---|
|
Get SLA details for issues based on JQL
Method | GET |
---|---|
URL | /rest/tts-api/1.0/sla/issue/ |
Possible query parameters | |
---|---|
-slaId | [Optional] sla filtering parameter Example slaId=26 |
-jql | Jql to filter issues that you want to get SLA details. Example jql=key in (ABC-34,ABC-35) |
-index | the index of a result whose page you want the pager to start at |
-max | the maximum number of results in a page (cannot be greater than 100) |
Response
Result |
---|
|
Get 'Time to SLA' field for the issue
Method | GET |
---|---|
URL | /rest/tts-api/1.0/sla/timeToSla/{issue-key} |
Possible Responses |
---|
|
Possible Responses |
---|
|
Get 'SLA Overview' data for the issue
Method | GET |
---|---|
URL | /rest/tts-api/latest/sla/overview/{issue-key} |
Possible Responses |
---|
|
Generating SLA data for existing issues
Method | GET |
---|---|
URL | /rest/tts-api/latest/sla/regenerate/{issue-key} |
Possible Responses |
---|
|
Resetting SLA
Method | POST |
---|---|
URL | /rest/tts-api/latest/sla/reset/{issue-id}/{sla-id} |
POST form param | "date=timeAsMillis"Â Â (as long, time millis, optional, if not set current time will be used) |
{issue-id} required parameter where {sla-id} is optional. If {sla-id} is not provided, then all SLAs for the issue will be reset. |
Possible Responses |
---|
|
Get SLA History
Method | GET |
---|---|
URL |
|