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 upstream Snaps:  Any Snap which has a Document output view
  • Expected downstream Snaps:  Any Snap which has a Document input view

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". 

  • Expected output:  If the Snap is executed successfully, it provides an output document with the status code of 204 under the "statusLine" key.

 

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:
InputThis Snap has exactly one input view and receives documents in the view. The Snap provides the schema on the input view.
OutputThis Snap has at most one output view and produces documents in the view. Each document contains the response data from the JIRA REST API service endpoint.
ErrorThis Snap has at most one document error view and produces zero or more documents in the view. Each document contains the response from the JIRA REST API service endpoint.

 

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:

  • Validate & Execute: Performs limited execution of the Snap, and generates a data preview during Pipeline validation. Subsequently, performs full execution of the Snap (unlimited records) during Pipeline runtime.
  • Execute only: Performs full execution of the Snap during Pipeline execution without generating preview data.
  • Disabled: Disables the Snap and all Snaps that are downstream from it.

 

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

 Click to view/expand
ReleaseSnap Pack VersionDateTypeUpdates
August 2022main17386 StableUpgraded with the latest SnapLogic Platform release.
4.29main15993 StableUpgraded with the latest SnapLogic Platform release.
4.28main14627 StableUpgraded with the latest SnapLogic Platform release.

4.27

main12833

 

Stable

Upgraded with the latest SnapLogic Platform release.
4.26main11181 StableUpgraded with the latest SnapLogic Platform release.
4.25 Patch425patches10571 Latest

Enhanced the JIRA Snap Pack to support HTTP Proxy Authentication.

4.25main9554
 
Stable

Upgraded with the latest SnapLogic Platform release.

4.24main8556
StableUpgraded with the latest SnapLogic Platform release.
4.23main7430
 
StableUpgraded with the latest SnapLogic Platform release.
4.22main6403
 
StableUpgraded with the latest SnapLogic Platform release.
4.21snapsmrc542

 

StableUpgraded with the latest SnapLogic Platform release.
4.20snapsmrc535
 
StableUpgraded with the latest SnapLogic Platform release.
4.19snaprsmrc528
 
StableUpgraded with the latest SnapLogic Platform release.
4.18snapsmrc523
 
StableUpgraded with the latest SnapLogic Platform release.
4.17ALL7402
 
Latest

Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers.

4.17snapsmrc515
 
Latest

Added the Snap Execution field to all Standard-mode Snaps. In some Snaps, this field replaces the existing Execute during preview check box.

4.16snapsmrc508
 
StableUpgraded with the latest SnapLogic Platform release.
4.15snapsmrc500
 
StableUpgraded with the latest SnapLogic Platform release.
4.14snapsmrc490
 
StableUpgraded with the latest SnapLogic Platform release.
4.13

snapsmrc486

 
StableUpgraded with the latest SnapLogic Platform release.
4.12

snapsmrc480

 
StableUpgraded with the latest SnapLogic Platform release.
4.11snapsmrc465
 
StableUpgraded with the latest SnapLogic Platform release.
4.10

snapsmrc414

 
StableUpgraded with the latest SnapLogic Platform release.
4.9snapsmrc405
 
StableUpgraded with the latest SnapLogic Platform release.
4.8

snapsmrc398

 
StableUpgraded with the latest SnapLogic Platform release.
4.7

snapsmrc382

 
StableUpgraded with the latest SnapLogic Platform release.
4.6snapsmrc362
 
StableUpgraded with the latest SnapLogic Platform release.
4.5.1

snapsmrc344

 
StableUpgraded with the latest SnapLogic Platform release.
4.5

snapsmrc344

Stable

Enhanced the error view output to include error, reason, and resolution.

4.4
 Stable

JIRA Search now has the Ignore empty result option.