Rovo MCP creates duplicate Jira tickets for a single request

[Ashutosh Kaushik]

When creating Jira tickets via Atlassian Rovo MCP Server, a single natural-language request results in multiple duplicate Jira issues being created instead of just one.

Environment

Tool: Atlassian Rovo MCP Server

Integration: Jira Cloud

Steps to Reproduce

1. Send a single instruction to Rovo, for example:
   “Create a Jira ticket and assign it to me for developing the UI for the Dashboard screen of SaaSDashboard.”

2. Rovo processes the request and creates Jira issues.

Expected Behavior
Rovo should create exactly one Jira ticket per user request.

Actual Behavior
Rovo creates two identical Jira tickets with:

• Same title

• Same description

• Same assignee

• Same priority

Example duplicates created:

• DEV-10 and DEV-11

• DEV-8 and DEV-9

These had to be manually closed and marked as duplicates.

Suggested Fix

• Ensure Rovo MCP executes exactly one create-issue API call per user intent

[Dr Valeri Colon _Connect Centric_]

Hi @Ashutosh Kaushik This usually happens when the request is interpreted as multiple actionable intents or when the client retries the same MCP action (for example due to timeouts or retries at the transport layer). MCP doesn’t currently guarantee idempotency for create-issue actions. Workarounds: add explicit wording like “create one Jira issue,” implement a client-side dedup check (e.g., search before create), or include a unique marker/label per request. If it persists, report it with timestamps and requestIds so Atlassian can trace duplicate executions.