JIRA Transition
On this Page
Snap type: | Write
| |||||||
|---|---|---|---|---|---|---|---|---|
Description: | This Snap performs a transition on a JIRA issue. When performing the transition you can update or set other issue fields by supplying input document.
Expected input: Input document should contain Issue ID and Transition ID at the minimum. An example input data would be: { id: 14556, transition: { } }
Transition ID indicates the transition action you can take on a JIRA issue specified by the "id" field above. You can get a list of the possible Transition ID's in a given JIRA issue by executing a JIRA Search Snap with the "jql" property value of "id = 14556" and the "expand" property value of "transitions".
| |||||||
| Prerequisites: | [None]
| |||||||
| Support and limitations: | Works in Ultra Pipelines. | |||||||
| Account: | This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. The Snap supports the JIRA basic auth account.
| |||||||
| Views: |
| |||||||
Settings | ||||||||
Label
| Required. The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline. | |||||||
API version
| Required. The JIRA REST API version number. Example: 2 Default value: 2
| |||||||
Snap execution | Select one of the three modes in which the Snap executes. Available options are:
| |||||||
Examples
An example input data would be:
{
id: 14556,
transition: {
id: 11
}
}
Transition ID indicates the transition action you can take on a JIRA issue specified by the "id" field above. You can get a list of the possible Transition ID's in a given JIRA issue by executing a JIRA Search Snap with the "jql" property value of "id = 14556" and the "expand" property value df "transitions".
An example of output data would be:
[
{
"headers": {
"strict-transport-security": "max-age=315360000;includeSubdomains",
"x-content-type-options": "nosniff",
"x-seraph-loginreason": "OK",
"connection": "keep-alive",
"set-cookie": "atlassian.xsrf.token=BWCK-SR48-JN93-ESFC|d611d6270cff68524982ee8a0f5e1005382d0c42|lin; Path=/; Secure",
"content-type": "application/json;charset=UTF-8",
"date": "Tue, 05 Aug 2014 01:29:58 GMT",
"x-arequestid": "1109x206x1",
"x-asen": "SEN-2848532",
"content-length": "0",
"x-asessionid": "5h6q3c",
"cache-control": "no-cache, no-store, no-transform",
"x-ausername": "admin",
"server": "nginx"
},
"statusLine": {
"reasonPhrase": "No Content",
"statusCode": 204,
"protoVersion": "HTTP/1.1"
},
"entity": "No Content",
"original": {
"id": "14556",
"transition": {
"id": "11"
}
}
}
]
An example of error view data would be:
[
{
"statusCode": 400,
"headers": {
"x-content-type-options": "nosniff",
"x-seraph-loginreason": "OK",
"connection": "keep-alive",
"set-cookie": "atlassian.xsrf.token=BWCK-SR48-JN93-ESFC|29371f74d4773247dac77f8a072a9f51e64c07da|lin; Path=/; Secure",
"content-type": "application/json;charset=UTF-8",
"date": "Tue, 05 Aug 2014 01:57:01 GMT",
"x-arequestid": "1137x213x1",
"x-asen": "SEN-2848532",
"content-length": "294",
"x-asessionid": "as4v5l",
"cache-control": "no-cache, no-store, no-transform",
"x-ausername": "admin",
"server": "nginx"
},
"error_entity": "{\"errorMessages\":[\"It seems that you have tried to perform a workflow operation (Start Progress) that is not valid for the current state of this issue (JIRASNAP-2975). The likely cause is that somebody has changed the issue recently, please look at the issue history for details.\"],\"errors\":{}}",
"error": "REST API service endpoint returned error result: status code = 400, reason phrase = Bad Request",
"request_headers": [
{
"authorization": "Basic YWRtaW46c25hcDEyMzQ=",
"content-type": "application/json"
}
],
"original": {
"id": "14556",
"transition": {
"id": "11"
}
}
}
]
See Also
Snap Pack History
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.