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. 😉