Why is it not possible to assign Rovo agents to columns in enterprise-managed projects?

[Jean Gustavo Horn]

I was checking some updates on the use of AI on Atlassian platforms, specifically Rovo. However, when trying to use it, I noticed that this functionality of agents working on specific statuses/columns only works in projects of the type "Team-managed business projects". Why is it restricted to only this model? Do you have any tips on using Rovo to help with day-to-day work?

[Kevin Kadakas · Accepted solution]

Hello @Jean Gustavo Horn 

Welcome to the community ✨

This could also be related to feature rollout differences between instances, since Atlassian often releases new Rovo capabilities gradually.

However, if your main goal is to automate actions when a work item moves to a specific status/column, you could also achieve this with a Jira Automation rule (now also referred to as a flow in some newer Atlassian experiences).

For example:

1. Trigger: Work item transitioned to status: [status name assigned to the column]
2. Action: Assign work item and assign it to the desired agent.

That approach currently gives much more flexibility and works well across different project types, including company-managed projects.

If this answer helped, please mark it as the accepted answer so others with the same issue can find it more easily.

[Jean Gustavo Horn]

Thank you for your reply. 😉

[Donald677]

Great catch, and yes, you're absolutely right! Rovo agents currently only work with specific statuses or columns in team-managed business projects, not enterprise-managed ones. So why the restriction? It comes down to complexity. Enterprise-managed projects have deeper permission structures, custom workflow rules, and multiple role-based controls that make it harder for Rovo agents to trigger cleanly. Atlassian started with team-managed projects to test and refine the feature before rolling it out to enterprise environments.

That said, you can still use Rovo agents in enterprise projects for things like auto-commenting on issues, summarizing ticket content, or suggesting status transitions, just not column-specific triggers yet. Want to get more creative with how you track and visualize Rovo's role in your daily workflows? You can visit here for some practical ideas. Hopefully, Atlassian brings full enterprise support soon. Hang in there!