Atlassian Jira CreateComment
CertifiedAdd a comment to a Jira issue
Atlassian Jira CreateComment
Add a comment to a Jira issue
Renders the issue key and comment body, serializes the request as JSON, then posts to /rest/api/2/issue/{issueIdOrKey}/comment. Uses the same authentication fields as other Jira tasks.
type: io.kestra.plugin.jira.issues.CreateCommentExamples
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: https://your-domain.atlassian.net
username: your_email@example.com
password: "{{ secret('JIRA_API_TOKEN') }}"
issueIdOrKey: "TID-53"
body: "This ticket is not moving, do we need to outsource this!"
Create a Jira issue, then comment on it in the same flow using its output key.
id: jira_flow
namespace: company.myteam
tasks:
- id: create_issue
type: io.kestra.plugin.jira.issues.Create
baseUrl: https://your-domain.atlassian.net
username: your_email@example.com
password: "{{ secret('JIRA_API_TOKEN') }}"
projectKey: myproject
summary: "Workflow failed"
description: "{{ execution.id }} has failed on {{ taskrun.startDate }}"
issueTypeId: "10001"
- id: log_issue_url
type: io.kestra.plugin.core.log.Log
message: "Created {{ outputs.create_issue.key }} — {{ outputs.create_issue.url }}"
- id: create_comment_on_a_ticket
type: io.kestra.plugin.jira.issues.CreateComment
baseUrl: https://your-domain.atlassian.net
username: your_email@example.com
password: "{{ secret('JIRA_API_TOKEN') }}"
issueIdOrKey: "{{ outputs.create_issue.key }}"
body: "Linked automatically from the same flow run."
Properties
baseUrl *string
1Jira REST base URL
Rendered HTTPS root such as https://your-domain.atlassian.net; the task appends the REST route before sending the request. A trailing slash is tolerated and stripped.
body *string
1Comment text
Rendered markdown or text sent as the Jira comment body.
issueIdOrKey *string
1Issue key or id to comment
Rendered value appended to /rest/api/2/issue/ before /comment.
accessToken string
Jira OAuth access token
Bearer token for OAuth; used only when username/password are not both set.
assets
Assets this task consumes as inputs or produces as outputs, for lineage tracking and the asset graph (Enterprise Edition). A flow declaring this property on a task is rejected in the open-source edition.
io.kestra.core.models.assets.AssetsDeclaration
IGNOREFAILWARNAsset failure behavior
Behavior applied to the task state when a declared asset fails to render, emit, or be persisted (e.g. a lock conflict): FAIL escalates it to FAILED, WARN (default) warns it if it would otherwise succeed, IGNORE leaves the state untouched.
Whether to auto-register assets referenced dynamically at runtime that are not statically declared in inputs or outputs.
The assets consumed as inputs.
io.kestra.core.models.assets.AssetIdentifier
1The assets produced as outputs.
io.kestra.plugin.ee.assets.Dataset
1150{}1150io.kestra.plugin.ee.assets.File
1150{}1150io.kestra.plugin.ee.assets.Table
1150{}1150io.kestra.plugin.ee.assets.VM
1150{}1150io.kestra.core.models.assets.External
1150{}1150io.kestra.core.models.assets.Custom
11501Custom asset type
{}1150options
HTTP client configuration
io.kestra.core.http.client.configurations.HttpConfiguration
falseIf true, allow a failed response code (response code >= 400)
List of response code allowed for this request
The authentication to use.
io.kestra.core.http.client.configurations.BasicAuthConfiguration
The password for HTTP basic authentication.
The username for HTTP basic authentication.
io.kestra.core.http.client.configurations.BearerAuthConfiguration
The token for bearer token authentication.
io.kestra.core.http.client.configurations.DigestAuthConfiguration
The password for HTTP Digest authentication.
The username for HTTP Digest authentication.
UTF-8The default charset for the request.
java.nio.charset.Charset
trueWhether to enable TCP Keep-Alive extended socket options (TCP_KEEPIDLE, TCP_KEEPINTERVAL, TCP_KEEPCOUNT).
Set to false when running on Windows workers, as these extended socket options are not supported by the Windows JDK and will cause connection failures.
trueWhether redirects should be followed automatically.
REQUEST_HEADERSREQUEST_BODYRESPONSE_HEADERSRESPONSE_BODYThe enabled log.
The proxy configuration.
io.kestra.core.http.client.configurations.ProxyConfiguration
The address of the proxy server.
The password for proxy authentication.
The port of the proxy server.
DIRECTDIRECTHTTPSOCKSThe type of proxy to use.
The username for proxy authentication.
The SSL request options
io.kestra.core.http.client.configurations.SslOptions
Whether to disable checking of the remote SSL certificate.
Only applies if no trust store is configured. Note: This makes the SSL connection insecure and should only be used for testing. If you are using a self-signed certificate, set up a trust store instead.
The timeout configuration.
io.kestra.core.http.client.configurations.TimeoutConfiguration
The time allowed to establish a connection to the server before failing.
PT5MThe time allowed for a read connection to remain idle before closing it.
password string
Jira password or API token
Used with username for Basic/API token authentication; ignored when an accessToken is provided.
payload string
Prepared JSON payload
Rendered JSON body sent as application/json when a task supports an explicit payload override.
username string
Jira username or email
Used with password for Basic/API token authentication; ignored when an accessToken is provided.
Outputs
id string
Created comment ID
Jira's internal identifier for the created comment.
issueIdOrKey string
Commented issue key or id
The rendered issueIdOrKey the comment was added to.
self string
Comment REST link
Jira's self REST API link for the created comment.
url string
Comment browse URL
Link to the issue in the Jira web UI with the new comment focused, built as {baseUrl}/browse/{issueIdOrKey}?focusedCommentId={id}.
