Jira - Edit Ticket | Alli Documentation

Overview

Trigger the execution to edit some commonly used fields on an existing Jira ticket

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/
Email	JIRA_EMAIL	Alphanumeric	✅	-	-	Email address associated with the api token
Ticket Key	JIRA_TICKET_KEY	Alphanumeric	✅	-	-	The ID of the ticket you wish to edit
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.
Assignee	JIRA_ASSIGNEE	Alphanumeric	➖	-	-	Email address of the assignee. If you like to use the project's default assignee pass in -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
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 - Edit Ticket
  inputs:
    JIRA_ACCESS_TOKEN: null  ## REQUIRED
    JIRA_EMAIL: null ## REQUIRED
    JIRA_TICKET_KEY: null ## REQUIRED
    JIRA_SUMMARY: null
    JIRA_DESCRIPTION: null
    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'