Rovo won't create a ticket in a Jira project anymore

Question

Hey Rovo community,

I build a custom Rovo to create Jira tickets for us, but as of two days ago, it keeps 'chasing its tail', and what I mean by that is that it keeps asking me to confirm the final ticket details and it keeps thinking an then asking the same question again.

Any thoughts or suggestions?

Thanks - Jamie

Jamie Nickerson · Answer

Hey everyone,

Thanks for all the great feedback.

I actually solved this with help from the above:

In the Tools Rovo uses, I changed it to Create Jira issues with advanced configuration and added Search By Query in Jira, Search with JQL, and Get work item. I was originally using only the Create Jira work item tool, which apparently wasn't robust enough to handle the instructions.

I feel foolish, since this was a simple fix, but I hope this helps someone else!

-Jamie

Ciro · Answer

Hey, one more data point.

Another thread this week has the same loop with a custom agent:

https://community.atlassian.com/forums/discussion/3316648/rovo-agents-in-an-eternal-please-review-loop

There, the author set the agent's Reasoning to Think deeper (Studio > your agent > Details > Reasoning, then Publish) and could finally see what was failing: the bulk "create work items" call was returning a 400 error, while creating items one at a time worked.

So two quick checks:

* Ask the agent for a single ticket and see if it still loops.
* If it does, look in the debug details for a 400 response and note which call it came from. That, plus the request ID, is what support will need.

Gabriela - LeanZero · Answer

Hi Jamie, I'd expect your agent to ask you to confirm once before it creates the ticket, but asking you the same question over and over isn't normal. Atlassian's agent actions page says it asks for confirmation before tools that change data, and that Jira work items sometimes need more input from you when there are required fields (https://support.atlassian.com/rovo/docs/agent-actions/).

That second part is where I'd start. I think the agent may be coming back to you for a field it can't fill. I'd name the exact space key and work item type in the agent's instructions, so it doesn't have to ask you or guess. Tool configuration in Agent Studio can pin those values, but right now it only covers Raise a request for service desks and a few Confluence tools, not the Jira create tool (https://support.atlassian.com/rovo/docs/configure-tools-for-rovo-agents/).

I'd also try creating the same ticket by hand in that space with that work item type, filling in every required field yourself. If someone added a required field or changed an allowed value about two days ago, that would explain why you keep getting the same question.

If nothing changed in the space, Arek's route is the next step. Support will want the request ID from the debug response.