Triage incoming bugs in Jira automatically

An Orkeste agent reads every new Jira bug, identifies the component, assesses severity from reproduction steps, and proposes an owner, waiting for the engineering lead's approval before assigning.

How the workflow runs

1. Detect new bug: Listens to Jira for new issues in the Bug issue type.
2. Classify component and severity: Reads description, steps and logs to infer component and severity.
3. Check for duplicates: Searches existing issues for likely duplicates and links them.
4. Engineering lead approves: Lead reviews proposed component, severity, owner and approves.
5. Update Jira: Applies fields and assigns the issue in Jira with full audit context.

Human-in-the-loop: Severity calls and owner assignments always require an engineering lead's explicit approval.

Works with your stack

• jira
• linear
• slack

Related workflows

• Auto-create sprint tickets in Jira from planning docs
• Detect blocked or silently stalled Linear issues
• Summarize sprint progress in Linear automatically

Questions about this workflow

What about security bugs?

Bugs flagged as security-related are routed to a dedicated reviewer and never auto-assigned.

Can it parse stack traces?

Yes. The classifier reads stack traces and logs to infer the component and likely owner.

What if the bug report is incomplete?

The agent posts a comment asking the reporter for the missing reproduction steps rather than guessing severity.