Hi Atlassian Community! 👋
I’m Swarna, a Product Manager on Jira Cloud Workflows team.
If you are a Jira Admin, you likely receive a steady number of requests from teams wanting to automate routine tasks and integrate AI agents into their day-to-day processes.
Today, AI agent rules in Jira workflows can only be configured by Space and Global Admins. This means admins often become the bottleneck for AI led team velocity gains, while end users resort to manually triggering agents ticket by ticket.
We are changing that! We are launching an exclusive Early Access Program (EAP) for End-User Agents in Jira Workflows, and we’d love for you to join us in shaping this experience.
🚀 What are End-User Agents in Jira Workflows?
This feature will allow individual team members to attach their preferred AI agents (Rovo, Studio, 1st-party, 3rd-party agents) directly to the workflow statuses they already use in their spaces from the Board view.
This agent added by the end user triggers only when that user transitions a work item to the status. No admin tickets, no workflow scheme editing required, no going to the work item view to manually trigger the preferred agent each time.
💡 Why this matters for Admins & Teams
- ⚡ Democratized AI adoption without admin bottleneck: Empower non-admin practitioners to automate their own agentic set ups (e.g., auto-generating test plans, drafting release summaries, reviewing code context) without altering the global workflow for the entire team.
- 🛡️ Admin governance & centralized visibility: As an admin, you retain full oversight. Admins can view all agents in a collated view inside the Workflow Editor and have the ability to manage or disable rules as needed.
- 🌱 Team discovery & cross-pollination: Team members can see which agents their peers are using on board statuses and clone/adopt high-performing agent setups for themselves.
🔍 How it compares
Capability | Admin-Configured Workflow Agents (Today) | End-User Workflow Agents (EAP) | Manual Triggers / Assign on work item view |
|---|
Who can configure agents? | Admins only | Any team member in the space | Any user per ticket |
Trigger condition | Triggers globally for all users who transition work item | Triggers only for the user who has set up the agent when they transition | Manual click / prompt |
Admin visibility | Workflow Editor | Workflow Editor (Consolidated view) with admin controls | Work item activity; No granular disable capability |
Setup location | Project / Workflow settings, Boards | Directly from Boards view | Work item view, manually select agent each time |
👥 Who are we looking for?
We are looking for a focused cohort of 10-15 Jira Cloud customers who:
- Have Jira Cloud - Standard, Premium, or Enterprise license(s).
- Have active teams using or exploring Rovo, 1P agents or custom Studio agents.
- Have Jira Boards that are linked only to one space (company or team managed)
Note: This EAP will require participation from both Jira users and their Space / Jira Admins.
🤝 What’s in it for you
- Direct influence on product design: Collaborate directly with our Product, Engineering, and Design teams to shape admin controls, UI placement, and future policy features before Beta & General Availability.
- High-touch support: Dedicated onboarding and direct Slack/email access to the engineering team.
🤝 What we ask
Commitment: Participation in a kick-off call, testing with 1–2 teams (upto 5 non-admin members) on your site, and a couple of 30-minute feedback sessions over the course of the EAP.
🗓️ Timeline
- EAP Kickoff: Early November 2026
- Program Duration: ~4–6 weeks of active feedback before moving to broader Beta.
🤝 Next action
Sign up now: End-user agents in Jira Workflows EAP Sign-up
Spots are limited to ensure high-touch collaboration. If you have questions about eligibility, security, or how end-user agents interact with your existing workflow schemes, drop a comment below!
Cheers,
Swarna Mehta
Product Manager, Jira Cloud Workflows
