CreateComment
Comment on a Jira ticket based on a workflow execution status.
type: "io.kestra.plugin.jira.issues.CreateComment"
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!"
YES
1
Atlassian URL
YES
1
The comment's content
YES
1
Jira ticket key
YES
1
Atlassian project's key
YES
Atlassian OAuth access token
(Required for OAuth authorization)
YES
Description of the ticket to be created
YES
Issue type ID of the Jira ticket
The issue type ID can be found using this URL : https://your-domain.atlassian.net/rest/api/2/issue/createmeta.
YES
Labels associated with opened ticket
NO
The HTTP client configuration.
YES
Atlassian password or API token
(Required for basic & API token authorization)
YES
Payload
YES
Summary of the ticket
YES
Atlassian Username
(Required for basic & API token authorization)
YES
duration
The time allowed to establish a connection to the server before failing.
YES
PT5M
duration
The time allowed for a read connection to remain idle before closing it.
NO
YES
The password for HTTP basic authentication.
YES
The username for HTTP basic authentication.
NO
false
If true, allow a failed response code (response code >= 400)
YES
List of response code allowed for this request
NO
The authentification to use.
NO
The password for HTTP basic authentication.
NO
The username for HTTP basic authentication.
NO
duration
The time allowed to establish a connection to the server before failing.
NO
duration
The time an idle connection can remain in the client's connection pool before being closed.
NO
UTF-8
The default charset for the request.
NO
true
Whether redirects should be followed automatically.
NO
ALL
TRACE
DEBUG
INFO
WARN
ERROR
OFF
NOT_SPECIFIED
The log level for the HTTP client.
NO
REQUEST_HEADERS
REQUEST_BODY
RESPONSE_HEADERS
RESPONSE_BODY
The enabled log.
NO
The maximum content length of the response.
NO
The proxy configuration.
NO
The address of the proxy server.
NO
The password for proxy authentication.
NO
The port of the proxy server.
NO
DIRECT
HTTP
SOCKS
The type of proxy to use.
NO
The username for proxy authentication.
NO
duration
The time allowed for a read connection to remain idle before closing it.
NO
duration
The maximum time allowed for reading data from the server before failing.
NO
The SSL request options
NO
The timeout configuration.
YES
The address of the proxy server.
YES
The password for proxy authentication.
NO
The port of the proxy server.
YES
DIRECT
DIRECT
HTTP
SOCKS
The type of proxy to use.
YES
The username for proxy authentication.
NO
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.
NO
YES
The token for bearer token authentication.