Unable to create Jira Tickets using Rovo

[Meena Vepa]

I am trying to provide a Confluence Page and ask Rovo to create Epics,  and Stories. But Rovo is not creating the tickets, it keeps asking me to confirm if all the information is good so it can create the tickets. Even after I confirm, Rovo doesn't create the Tickets. I tried this multiple times. Any Suggestions?

[Arkadiusz Wroblewski]

Hello @Meena Vepa 

Building on @James Gamble  answer, check which exact Rovo flow you are using, as Rovo Chat handles item creation differently than the Confluence page flow.

In case you're using Rovo Chat, try isolating the issue by requesting just a single Story. Rovo can struggle with complex bulk requests.When using Confluence page flow, manually review suggested items in the right-side panel.

If a single Story goes through, the blocker is likely a required field or a bulk limit. If even a single item gets stuck in a loop, it points/lead/say to a backend action failure and needs Atlassian...

We can help with Frontend UI. But Backend must be handled by Atlassian.

From a technical standpoint, if you troubleshoot something like that, you must simplify the concept because then you see the problem better.

Best,

Arkadiusz 🤠☀️

[James Gamble]

Hola Meena,

This sounds like Rovo can read the Confluence page and prepare the issue details, but something is blocking the actual Jira issue creation step.

I would check it in a few places.

First, try creating one Epic and one Story manually in the same Jira project using the same account. Use the same project and issue types that you want Rovo to create. If Jira prompts you to fill in required fields during manual creation, Rovo will need those values as well.

Next, check the project permissions. Open the Jira project, go to Project settings, then Permissions, and confirm that your account or one of your groups has the Create Issues permission. Also, confirm that Epic and Story are available issue types for that project.

After that, check the field configuration and screens for those issue types. If the project requires fields such as Team, Components, Fix Version, Sprint, Parent, labels, or any custom field, Rovo may not be able to create the issue unless those values are included in the request.

I would also test Rovo with the smallest possible request, for example: “Create one Story in project ABC with summary ‘Test story’ and description ‘Created as a Rovo test.’” If that works, the problem may be the larger request to create multiple Epics and Stories from the Confluence page. If that simple test still loops after you confirm, then the issue is probably with the Rovo agent’s available actions, permissions, or Jira project configuration.

If you are using a custom Rovo agent, check the agent configuration and ensure the Jira issue creation action/tool is enabled. If you are using regular Rovo chat, it may help draft Epics and Stories, but it cannot complete the creation step in your setup.

The main thing I would verify is whether manual issue creation works first. Once that is confirmed, test one simple Rovo-created issue, then build back up to the full Epic and Story creation request.

Thanks,

James