CreateComment

type: "io.kestra.plugin.jira.issues.CreateComment"

Comment on a jira ticket based on workflow execution status.

Examples

Comment on a jira ticket on a failed flow execution.

id: jira_flow
namespace: company.myteam

tasks:
  - id: create_comment_on_a_ticket
    type: io.kestra.plugin.jira.issues.CreateComment
    baseUrl: your-domain.atlassian.net
    username: your_email@example.com
    password: "{{ secret('jira_api_token') }}"
    projectKey: project_key
    issueIdOrKey: "TID-53"
    body: "This ticket is not moving, do we need to outsource this!"

Properties

baseUrl

• Type: string
• Dynamic: ✔️
• Required: ✔️
• Min length: 1

Atlassian URL

body

• Type: string
• Dynamic: ✔️
• Required: ✔️
• Min length: 1

The comment's content

issueIdOrKey

• Type: string
• Dynamic: ✔️
• Required: ✔️
• Min length: 1

Jira ticket key

projectKey

• Type: string
• Dynamic: ✔️
• Required: ✔️
• Min length: 1

Atlassian project's key

accessToken

• Type: string
• Dynamic: ✔️
• Required: ❌

Atlassian OAuth access token

(Required for OAuth authorization)

description

• Type: string
• Dynamic: ✔️
• Required: ❌

Description of the ticket to be created

issuetype

• Type: string
• Dynamic: ✔️
• Required: ❌
• Default: Task

Issue type of the Jira ticket

Examples: Story, Task, Bug (default value is Task)

labels

• Type: array
• SubType: string
• Dynamic: ✔️
• Required: ❌

Labels associated with opened ticket

password

• Type: string
• Dynamic: ✔️
• Required: ❌

Atlassian password or API token

(Required for basic & API token authorization)

payload

• Type: string
• Dynamic: ✔️
• Required: ❌

Payload

summary

• Type: string
• Dynamic: ✔️
• Required: ❌

Summary of the ticket

username

• Type: string
• Dynamic: ✔️
• Required: ❌

Atlassian Username

(Required for basic & API token authorization)

Outputs

Definitions