Jira Issues Create
CertifiedCreate a Jira issue
Jira Issues Create
Create a Jira issue
Builds a JSON payload from the rendered project, summary, description, labels, issue type, and priority, then posts it to /rest/api/2/issue/. summary and description are optional and omitted from the payload when not set; a kestra-bot label is always included.
type: io.kestra.plugin.jira.issues.CreateExamples
Create a jira ticket on a failed flow execution using basic authentication.
id: jira_flow
namespace: company.team
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 }} See the link below for more details"
labels:
- bug
- workflow
issueTypeId: "10001"
Create a jira ticket on a failed flow execution using OAUTH2 access token authentication.
id: jira_flow
namespace: company.myteam
tasks:
- id: create_issue
type: io.kestra.plugin.jira.issues.Create
baseUrl: https://your-domain.atlassian.net
accessToken: "{{ secret('your_jira_access_token') }}"
projectKey: myproject
summary: "Workflow failed"
description: "{{ execution.id }} has failed on {{ taskrun.startDate }} See the link below for more details"
labels:
- bug
- workflow
issueTypeId: "10001"
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.
projectKey *string
1Project key
Jira project key injected into the payload.
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
{}1150description string
Issue description
Rendered description text for the issue; templating supported.
issueTypeId string
Issue type ID
Optional Jira issue type ID; discover available values at https://your-domain.atlassian.net/rest/api/2/issue/createmeta.
labels array
Labels
Rendered list of labels added to the issue; kestra-bot is always included.
options
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.
Retry strategy for HTTP requests.
retry is disabled by default.
Constant retry
Retry with a fixed delay between attempts.
durationRETRY_FAILED_TASKRETRY_FAILED_TASKCREATE_NEW_EXECUTION>= 1durationfalseExponential retry
Retry with exponentially increasing delays between attempts.
durationdurationRETRY_FAILED_TASKRETRY_FAILED_TASKCREATE_NEW_EXECUTION>= 1durationfalseRandom retry
Retry with a random delay within a configurable range between attempts.
durationdurationRETRY_FAILED_TASKRETRY_FAILED_TASKCREATE_NEW_EXECUTION>= 1durationfalse[502,503,504]HTTP status codes that should be retried.
Used for idempotent methods (GET, HEAD) without their own entry in retryOnStatusCodesByMethod. Non-idempotent methods are never retried on a status code unless listed in retryOnStatusCodesByMethod. Defaults to 502, 503 and 504 for idempotent methods (GET, HEAD) only.
Per-HTTP-method overrides for which status codes should be retried.
Keys are HTTP methods (e.g. GET, POST). A method with no entry here falls back to retryOnStatusCodes. This lets a caller retry more broadly for safe, read-only methods (for example, every 5xx and a 429 for GET/HEAD) while keeping a narrower list for methods that write, where retrying a request that may have already been processed by the origin risks duplicating the effect. Example: {GET: [429, 500, 502, 503, 504], HEAD: [429, 500, 502, 503, 504]}.
["GET","HEAD"]HTTP methods for which any transport-level failure may be retried.
A transport-level failure is a connection or timeout error rather than an HTTP response (e.g. a read timeout or a connection reset mid-request). For a method listed here, any such failure is retried. Defaults to GET and HEAD HTTP methods.
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.
priority string
Priority
Optional Jira priority name such as Highest, High, Medium, Low or Lowest; it must exist in your Jira instance and be available on the create screen of the project.
summary string
Issue summary
Rendered summary for the issue; templating supported.
username string
Jira username or email
Used with password for Basic/API token authentication; ignored when an accessToken is provided.
Outputs
id string
Created issue ID
Jira's internal numeric identifier for the issue.
key string
Created issue key
Human-readable issue key such as PROJ-123; use it to reference the issue in downstream tasks.
self string
Issue REST link
Jira's self REST API link for the created issue.
url string
Issue browse URL
Link to the issue in the Jira web UI, built as {baseUrl}/browse/{key}.
