Overview
Adds a comment to a Jira ticket
Variables
|
Name |
Reference |
Type |
Required |
Default |
Options |
Description |
|---|---|---|---|---|---|---|
|
Ticket Key |
JIRA_TICKET_KEY |
Alphanumeric |
✅ |
- |
- |
You can usually find the ticket key in the ticket's URL or in the ticket's title. It typically consists of uppercase letters, followed by a hyphen, and then a numerical value. For example, in the ticket URL "https://jira.example.com/browse/PROJ-123", the ticket key is "PROJ-123". |
|
Comment |
JIRA_COMMENT |
Alphanumeric |
✅ |
- |
- |
This text will be posted as a comment to the Jira ticket |
|
Access Token |
JIRA_ACCESS_TOKEN |
Password |
✅ |
- |
- |
To generate a access token go to https://id.atlassian.com/manage-profile/security/api-tokens |
|
Email Address |
JIRA_EMAIL_ADDRESS |
Alphanumeric |
✅ |
- |
- |
The email address associated with the Access Token |
|
Domain |
JIRA_DOMAIN |
Alphanumeric |
✅ |
- |
- |
The subdomain of the jira instance for example it would be shipyard if the url is https://shipyard.atlassian.net/jira/software |
YAML
Below is the YAML template for this Template and can be used in the Fleet YAML Editor.
source:
blueprint: Jira - Add Comment To Ticket
inputs:
JIRA_TICKET_KEY: null ## REQUIRED
JIRA_COMMENT: null ## REQUIRED
JIRA_ACCESS_TOKEN: null ## REQUIRED
JIRA_EMAIL_ADDRESS: null ## REQUIRED
JIRA_DOMAIN: null ## REQUIRED
type: BLUEPRINT
guardrails:
retry_count: 1
retry_wait: 0h0m0s
runtime_cutoff: 1h0m0s
exclude_exit_code_ranges:
- '0'