why cant the agent use its skills to add jira objects in automation rules??

[Dirk]

I'm trying to create a automation in Jira 

I need to regularly create a new sprint and add jira tickets of a certain status to that sprint....simple

But I cant use the Rovo agent because for some dumb reason it says that, in automations, it cant use its skills that create jira objects.....WHY?

on top of that nonsense the more manual automation elements cannot simply add tickets to a sprint...there's a bunch of caveats to that....

Can Atlassian to allow us to give the Agent permission to use its skills to create Jira objects?

....then I can create simple automations around triggering its skills and reasoning

[Kai Krause · Accepted solution]

Hi and Welcome, 

when invoked from Automation, Rovo:

• ✅ Can reason
• ✅ Can transform data
• ✅ Can return structured output
• ❌ Cannot execute skills that create or modify Jira objects (issues, sprints, etc.)

This is intentional.

Automation rules run with elevated permissions. 

If Rovo were allowed to change objects you would effectively have and AI that autonomous works. That’s a governance and audit nightmare for Atlassian Cloud.

Coul dbe that Atlassian change this , today that boundary is deliberate.

But you can do it with a native automation . 

Triger
Webrequest against sprint api 

POST /rest/agile/1.0/sprint

to create a sprint

Set Created sprint id to the selected issues and you avoid the AI unpredictability.

BR
Kai 

 

[Dr Valeri Colon _Connect Centric_]

In other words @Dirk... in automation rules, Rovo agents can analyze and return output, but they can’t directly create, update, or delete content. Atlassian documents this limit for agents in automations, so the workaround is to have the agent return something structured with {{agentResponse}}, then let native Automation or the Jira API do the sprint creation and issue updates.