Where to Put the Human Check When You Combine Jira Automation and AI

Automation rules do exactly what you tell them. AI-generated text and queries can be close but not quite right. Put them together and a small error can repeat across hundreds of issues.

Short answer: let AI draft, let a person approve, and only then let automation act.

If a rule posts an AI-written summary to a ticket, have it post as an internal comment first. A person reads it and decides whether to share it with the customer.

When a rule uses a generated query, run it on one project, or add a label condition, before widening it. Check the audit log after the first few runs.

Bulk transitions, deletions and customer-facing emails should wait for a person's sign-off. Comments and labels are easy to undo, so they are safer starting points.

Add a note in the rule description: what the AI step is expected to produce and who reviews it. Six months later, someone will need to know.

If you answer "no" to any of these, add a manual step.

What's the first automation rule you would trust with an AI step?

Disclosure: I work with Empyra, an Atlassian Platinum Solution Partner in Irving, Texas and Bangalore. More at atlassian intelligence services.