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.

[Sami Shaik]

Hi @Milena Esther de Sá ,

Two separate things are going on here, and neither is your configuration.

1. The Automation UI isn't hiding anything from you. Jira Cloud Automation has never had native "Start sprint" or "Complete sprint" actions. There's a Create sprint action, but sprint state changes have been an open feature request for years (JSWCLOUD-20944). The only sprint-completion change Atlassian shipped in 2026 is a nicer manual Complete sprint dialog. Nothing for Automation.

2. Your agent almost certainly changed with the Rovo model migration. Atlassian migrated all Rovo agents to a new backend LLM model, mandatory as of March 31, 2026. The announcement thread has many reports exactly like yours: agents that worked before now claim missing permissions or stop performing actions they used to do. Changing sprint state was never a documented Rovo skill, so your old agent was achieving it through behavior the new model no longer attempts. Moving issues between sprints still works because that's ordinary issue editing, which is supported.

The reliable fix: take the sprint lifecycle out of the AI's hands entirely.

1. Scheduled Automation rule (or whatever trigger fits your flow)
2. Send web request action to the Agile REST API: POST /rest/agile/1.0/sprint/{sprintId}
   • Start: body {"state":"active"}. The sprint must be in 'future' state and have startDate and endDate set, or you get a 400.
   • Complete: body {"state":"closed"}. The sprint must be 'active'. Jira sets completeDate itself.
   • Authenticate with an API token. If you get 403, the token's account lacks Manage Sprints on a project in the board filter.
3. Keep the Rovo agent for what it's good at: moving incomplete items, writing the sprint summary, commenting. Deterministic state changes via the API, judgment via the agent.

If you'd rather not maintain web requests, Marketplace apps exist that auto-start and auto-complete sprints by date.

Since your regression matches the post-migration pattern, also open a support ticket and reference the model migration. Atlassian has explicitly asked for these reports.