Create Jira Issues Automatically for Incident Management

Turn every Kestra workflow failure into a tracked Jira issue automatically. This system-level blueprint listens for failed and warning executions across your namespaces and opens a Jira ticket enriched with execution metadata, so incidents land in your engineering backlog the moment they happen instead of going unnoticed in logs. It solves the classic operational gap where a pipeline fails silently and nobody finds out until a downstream consumer complains.

How it works

1. A flow trigger of type io.kestra.plugin.core.trigger.Flow watches executions across the platform.
2. An io.kestra.plugin.core.condition.ExecutionStatus condition narrows the trigger to executions ending in FAILED or WARNING.
3. An io.kestra.plugin.core.condition.ExecutionNamespace condition with comparison: PREFIX scopes the trigger to the company namespace prefix, so only your own flows raise tickets.
4. When a matching execution is detected, the create_ticket task (io.kestra.plugin.jira.issues.Create) opens a Jira issue under the configured projectKey, with a summary, a description populated from {{ trigger.executionId }} and {{ taskrun.startDate }}, and the labels bug and workflow.

What you get

• Automatic Jira tickets for every failed or warning execution, no manual triage.
• Tickets enriched with the execution ID and failure timestamp for fast lookup.
• Consistent labeling (bug, workflow) for filtering and reporting in Jira.
• One central system flow covering all flows under a namespace prefix.

Who it's for

• DevOps and platform engineering teams that run Jira as their incident system of record.
• SRE and reliability teams that need failures surfaced as actionable work items.
• Data and analytics engineers who want pipeline failures visible to the whole team.

Why orchestrate this with Kestra

Jira itself has no awareness of your pipelines, and most schedulers cannot react to the failure of an unrelated workflow. Kestra closes that gap with event-driven flow triggers that fire on the status of any execution across namespaces, not just on a clock. You get retries, full execution lineage, and a declarative YAML definition that lives in version control, so your incident-response logic is reviewable, reusable, and consistent across every team.

Prerequisites

• A Kestra instance with the Jira plugin available.
• A Jira Cloud account with a project and permission to create issues.

Secrets

• JIRA_API_TOKEN: a Jira API token used as the password for authentication.

Quick start

1. Add the JIRA_API_TOKEN secret to your Kestra instance or namespace.
2. Set baseUrl, username, and projectKey on the create_ticket task to match your Jira Cloud instance.
3. Adjust the ExecutionNamespace namespace value so the prefix matches the flows you want to monitor.
4. Deploy the flow, then run any failing flow under that namespace and confirm a Jira issue is created.

How to extend

• Add ExecutionLabels conditions to ticket only specific tiers or owners.
• Branch on severity to route critical failures to a different projectKey or priority.
• Append a Slack or email notification task alongside the Jira issue for faster awareness.
• Enrich the description with the failed task ID, error message, or a direct link to the execution.

Links

• Jira plugin documentation