Overview
Triggers the execution to create a ticket in Jira.
Variables
|
Name |
Reference |
Type |
Required |
Default |
Options |
Description |
|---|---|---|---|---|---|---|
|
Access Token |
JIRA_ACCESS_TOKEN |
Password |
✅ |
- |
- |
https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/ |
|
|
JIRA_EMAIL |
Alphanumeric |
✅ |
- |
- |
Email that is associated with the api token |
|
Domain |
JIRA_DOMAIN |
Alphanumeric |
✅ |
- |
- |
The sub-domain of your Jira instance. For example if your jira instance url is https://shipyard.atlassian.net/ this value would be shipyard |
|
Project Key |
JIRA_PROJECT_KEY |
Alphanumeric |
✅ |
- |
- |
The unique identifier for the Jira project where the ticket will be created.Normally 3-4 letters long |
|
Parent Ticket Key |
JIRA_PARENT_TICKET_KEY |
Alphanumeric |
➖ |
- |
- |
The key of the parent ticket if you want to create a subtask under an existing ticket. |
|
Summary |
JIRA_SUMMARY |
Alphanumeric |
✅ |
- |
- |
A short summary or title describing the issue or task of the ticket. |
|
Description |
JIRA_DESCRIPTION |
Alphanumeric |
➖ |
- |
- |
A detailed description of the ticket, providing additional context or information. |
|
Issue Type |
JIRA_ISSUE_TYPE |
Alphanumeric |
✅ |
|
- |
The type of the ticket, such as bug, task, improvement, or story |
|
Assignee |
JIRA_ASSIGNEE |
Alphanumeric |
➖ |
- |
- |
Email address of the User you want to assign the ticket to. If you would like for this to be the default assignee for the project use -1 |
|
Labels |
JIRA_LABELS |
Alphanumeric |
➖ |
- |
- |
Labels to tag and categorize the ticket. Multiple labels can be assigned by separating them with commas. |
|
Components |
JIRA_COMPONENTS |
Alphanumeric |
➖ |
- |
- |
Components of the Jira project to associate with the ticket. |
|
Due Date |
JIRA_DUE_DATE |
Alphanumeric |
➖ |
- |
- |
The due date you wish to assign the ticket |
|
Priority |
JIRA_PRIORITY |
Alphanumeric |
➖ |
- |
- |
The priority level of the ticket, indicating its importance or urgency. |
YAML
Below is the YAML template for this Template and can be used in the Fleet YAML Editor.
source:
blueprint: Jira - Create Ticket
inputs:
JIRA_ACCESS_TOKEN: null ## REQUIRED
JIRA_EMAIL: null ## REQUIRED
JIRA_DOMAIN: null ## REQUIRED
JIRA_PROJECT_KEY: null ## REQUIRED
JIRA_PARENT_TICKET_KEY: null
JIRA_SUMMARY: null ## REQUIRED
JIRA_DESCRIPTION: null
JIRA_ISSUE_TYPE: Task ## REQUIRED
JIRA_ASSIGNEE: null
JIRA_LABELS: null
JIRA_COMPONENTS: null
JIRA_DUE_DATE: null
JIRA_PRIORITY: null
type: BLUEPRINT
guardrails:
retry_count: 1
retry_wait: 0h0m0s
runtime_cutoff: 1h0m0s
exclude_exit_code_ranges:
- '0'