In the space of a month, agents have picked up three separate doors into Jira, and I am genuinely unsure where the gate belongs. Curious how others are handling this, because I do not have it figured out.
The three doors, all checked in my own instance this week:
- Workflow rules. The new editor's Perform actions includes Trigger agent action: a transition can invoke a Rovo agent.
- Automation rules. My rule builder already shows a Use Agent action today, and this week's Atlassian Cloud changes post lists a Claude agent action rolling out too.
- Direct assignment. Claude Agent for Jira (the Marketplace beta, announced by Atlassian in June) makes the agent an assignee. The admin thread here from a few weeks back covers its gaps well, including that nothing restricts who can trigger it.
Here is what makes this tricky: each door has a different lock, and none of the locks is about the agent. Workflows are gated by who edits workflows. Automation is gated by who edits rules, but a rule fires for anyone who triggers it. Assignment is gated by whether the app is installed, full stop. The org-level agent policies mentioned in this week's changes post are not visible on my site yet, so for now that layer is a promise, not a control.
So, two honest questions:
- Where are you putting the gate today: workflow design, automation governance, app installation, or nowhere yet?
- What did you allow an agent to do first, and what is still off the table?
Even a one-line "we have not touched any of it yet" is a useful answer. That is data too.
