On this Page
Table of Contents | ||||
---|---|---|---|---|
|
Snap type: | Write | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description: | This Snap provides the functionality to execute the HTTP Put method to a JIRA REST API service endpoint to update JIRA issues.
| |||||||||||||
Prerequisites: | [None] | |||||||||||||
Support and limitations: |
| |||||||||||||
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 | The JIRA REST API version number. Example: 2 Default value: 2 | |||||||||||||
|
|
Examples
For a simple update to a JIRA item, you can use a simple Mapper + JIRA Update pipeline.
When the JIRA Update Snap has a valid account, the target schema is displayed in the Mapper Snap.
Specify the ID of the JIRA issue by mapping a value to $id, then update the fields you need to. In the following screen, JIRA issue FULL-8 will update the Assignee in JIRA to the value of the pipeline parameter _assignee.
Use the JIRA Get fields API to determine what your custom fields are.
Related Examples
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|