Agent created in Atlassian Studio fails to complete and start Sprints (Company-managed project)

[Milena Esther de Sá]

Hi everyone,

I’m experiencing a critical change in behavior with a custom Rovo Agent created within Atlassian Studio. I’m trying to figure out if this is a platform-wide restriction or a recent change.

The Situation:
I have an automation flow for a Company-managed project where a Rovo Agent is responsible for managing the sprint lifecycle (moving incomplete items and closing the sprint).

The Problem:

1. The Agent's Failure: The Agent can still move issues between sprints, but it is now unable to "Complete" or "Start" a sprint. It seems the Agent has lost the specific "Skill" or API scope required to change the sprint state, even though it has full project access.

2. Automation UI: In the Jira Automation builder, the "Complete sprint" and "Start sprint" actions are not visible in the list of available actions.

Crucial Context:
It is important to note that while these actions might not have been explicitly visible as "buttons" in the Automation UI in the past, the automated process used to work seamlessly. Whether through AI instructions or background triggers, the sprints were being managed automatically. Now, the flow is broken, and the actions are nowhere to be found in the UI.

My questions:

• Has Atlassian recently restricted Atlassian Studio Agents from accessing the Sprint lifecycle?

• Is there a new requirement to explicitly enable "Sprint Management" skills for Agents created in Studio?

Any insights from the Community, Rovo or Automation product teams would be greatly appreciated.