Rovo Bot Fails to Create Jira Ticket on First Attempt – Requires Manual Retry

[Dor Blayzer]

Problem Description

I've configured a custom Rovo Bot to automatically create structured bug tickets in Jira from user descriptions. The bot is designed to immediately generate a complete bug report with all required fields (Summary, Description, Environment, Steps to Reproduce, etc.) whenever a user mentions an issue.

The Issue:
The bot does not create the Jira ticket on the first attempt. Instead, I have to explicitly ask it to "create the ticket" or "do it again" in a follow-up message before it actually executes the agent_action_jira_issue_create action.

Expected Behavior

When I provide an issue description, the bot should:

1. Parse and structure the bug report
2. Automatically create the Jira ticket immediately using the configured action
3. Confirm ticket creation with the ticket number/link

Actual Behavior

When I provide an issue description, the bot:

1. Parses and structures the bug report correctly
2. Displays the formatted bug report in the chat
3. Does NOT create the Jira ticket
4. Only creates the ticket when I send a second message asking it to do so

Environment

• Platform: Atlassian Rovo (Jira Cloud)
• Bot Configuration: Custom agent with Jira issue creation action enabled
• Action ID: agent_action_jira_issue_create
• Scenario ID: f7371bc8-c21e-4645-95bf-5c98dae05feb

Debug Information

The bot's response metadata shows:

{
"scenario": {
"id": "f7371bc8-c21e-4645-95bf-5c98dae05feb",
"name": "Agvengers Flow",
"actionIds": ["agent_action_jira_issue_create"]
},
"actions": [],
"plugin_invocations": []
}

Notice that "actions": [] is empty on the first attempt, even though the action is configured in the scenario.

Bot Instructions (Relevant Excerpt)

My bot is instructed to:

• "Create a new bug ticket whenever the user mentions an issue"
• "Always output the bug report" with structured fields
• Include specific formatting rules and behavior guidelines

The instructions emphasize immediate ticket creation, but the bot seems to only format the report without triggering the action.

Questions

1. Is there a known issue with action execution requiring explicit user confirmation or follow-up prompts?
2. Do I need to modify my bot's instructions to explicitly call the action programmatically?
3. Is there a configuration setting that controls whether actions auto-execute vs. require manual triggering?

What I've Tried

• Verified the agent_action_jira_issue_create action is enabled in the scenario
• Reviewed bot instructions for clarity around automatic ticket creation
• Checked permissions and action configurations

Any guidance on ensuring the Jira action executes on the first attempt would be greatly appreciated!

[Mohanraj Thangamuthu · Accepted solution]

Hello, Good day. I have created a support request with the concerned team and our team will get back to you over email. Thanks

[Dr Valeri Colon _Connect Centric_]

@Dor Blayzer @Clark Everson This usually happens because Rovo agents often don’t auto-run write actions on the first message—they’ll draft the content, then wait for a clear “go ahead” to create/update items. That’s why you see actionIds configured but actions: [] empty. Fix: adjust the prompt/instructions to include an explicit trigger phrase (e.g., “After drafting, ask: ‘Create this ticket now? (Yes/No)’ and only run the action on Yes”), or require users to start with “Create a bug ticket:” so intent is unambiguous. If you truly need auto-create, check org safety settings/governance—some tenants enforce confirmation for write actions.

[Dor Blayzer]

@Clark Everson 
Any updates on this one?
It's really frustrating to ask the agent twice to create a simple ticket.

[Clark Everson]

Hi @Dor Blayzer 

Taking a look at this I found this ticket from the developer community: https://ecosystem.atlassian.net/browse/FRGE-1601

From what I could see it seems like it maybe a known issue as it does occur with Rovo service accounts, on a few threads over in the developer community. 

As yours is a bit different I escalated it to Atlassian as it seems from reviewing you tired everything.

Best,

Clark

[Abdel Guettatfi]

This is a question in the same context:
In creating the Jira, I am facing another issue: Rovo isn't setting the Team Assignment. We have several teams that can be selected through the interface, but Rovo isn't doing that. For example, the teams include Instructional Technology, Repair, IDM, etc. Any help is appreciated.
Abdel