On this Page
Table of Contents | ||||
---|---|---|---|---|
|
Snap type: | Write | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Description: | This Snap provides the functionality to execute the HTTP Delete method to a JIRA REST API service endpoint to delete JIRA issues.
| |||||||||||||
Prerequisites: | The user must have Delete permissions within JIRA. | |||||||||||||
Support and limitations: | Ultra pipelines: Works in Ultra Pipelines.Spark mode: Not supported in Spark mode | |||||||||||||
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 | |||||||||||||
|
|
Examples
You will likely want to use a Mapper Snap before the JIRA Delete Snap to see the target schema being requested and to map the appropriate fields or parameters.
At this time, the only item in the schema is id.
Insert excerpt | ||||||
---|---|---|---|---|---|---|
|