Skip to content
Workflow

Govern AI agents on Jira

Add governance controls to AI agents that triage, create, and update Jira issues. The Jira pack ensures agents follow your team's workflow conventions, require approval for status transitions, and maintain audit trails on every ticket change.

What this pack does

  • Policy enforcement on issue creation and transitions
  • Approval gates for priority escalations
  • Field validation before agent updates
  • Audit log of every agent-initiated change

Use cases

Require approval before an agent escalates issue priority

Validate that agents assign correct labels and components

Audit AI-driven triage decisions

Quick setup

  1. 1Install the Jira pack: cordumctl pack install jira
  2. 2Configure Jira API credentials
  3. 3Define workflow policies for issue transitions
  4. 4Enable the pack and test with your project

Frequently asked questions

Can I limit agents to specific Jira projects?

Yes. The Jira worker enforces a project allowlist, so agents only read and update the projects you authorize. Reads are permitted by default, while writes such as creating issues or moving them through a workflow are evaluated against policy first.

How do I require approval before an agent escalates issue priority?

Define a policy on the relevant status or field transition. When an agent attempts a priority escalation, the Safety Kernel returns a Require Approval decision and holds the change until a reviewer signs off, so high-impact triage decisions always have a human in the loop.

Can Cordum validate the fields an agent sets on a ticket?

Yes. Field validation runs before an agent update is applied, letting you enforce that labels, components, and assignees match your team's conventions. Updates that violate the rules are denied or constrained rather than silently written to Jira.

What record do we keep of AI-driven triage?

Every agent-initiated issue change is logged in the audit trail with the action, the governance decision, and any approver involved. That gives compliance and engineering leads a defensible history of which agent touched which ticket and why it was allowed.

Ready to govern Jira?

Other integrations