Cursor in Jira: Assign Tickets to Cloud Agents
CursorCursor launched a native Jira integration that lets teams assign Jira work items directly to Cursor's cloud agent, or trigger it via @Cursor mentions in issue comments. The agent reads the ticket's title, description, and comments, then autonomously fixes bugs, adds features, updates tests, or investigates the task — posting progress updates and linking the resulting pull request back in Jira. The integration requires Jira Commercial Cloud with Rovo enabled and is installed through the Cursor integrations dashboard.
Sources & Mentions
3 external resources covering this update
Cursor Lands in Jira: Cloud Agents Triggered by Ticket Assignment
Cursor introduced a native integration with Jira on May 19, 2026, enabling engineering teams to delegate development work directly from their project management workflow. Rather than switching between Jira and the IDE to kick off an agent session, teams can now assign a Jira issue to Cursor — and the cloud agent handles the rest.
How the Integration Works
There are two ways to engage the Cursor agent from within Jira. The first is direct assignment: open any issue and set the assignee to Cursor, just as you would assign it to a human teammate. The second is via comment mention: type @Cursor in any issue comment, optionally specifying parameters such as repo=acme/backend or model=gpt-5.5 to target a specific repository or model.
Once invoked, the agent analyzes the work item in full — reading the title, description, prior comments, and the team's repository settings to understand scope. Cursor then executes autonomously: fixing bugs, adding features, updating tests, or investigating the codebase as appropriate. When finished, it posts a status summary inside the Jira issue and includes a direct link to the generated pull request.
Authentication and Configuration
The integration supports two authentication modes. Under the service account model, all agents run under shared team settings, which is suitable for most automated workflows. Under user-level authentication, individual contributors connect their personal Cursor accounts so agents use their preferences and permissions.
Setup is handled through the Cursor integrations dashboard and requires installing the Cursor app from the Atlassian Marketplace. Once installed, teams configure default repositories, models, and branches through a brief Cloud Agent setup flow.
Requirements and Limitations
The integration requires:
- Jira Commercial Cloud with Rovo enabled
- Cursor admin access for the team
- GitHub or GitLab connected to Cursor
- Usage-based billing enabled (the integration does not work on flat-rate plans)
Notably, Privacy Mode (Legacy) is not supported — temporary code storage is required for the agent to operate. The integration is also not available for Atlassian HIPAA or FedRAMP (Government Cloud) instances at launch.
Context: Cursor Joins Jira's Agent Ecosystem
Cursor's entry into Jira comes as Atlassian has opened its platform to third-party AI agents more broadly. Jira's agent assignment model — originally launched with GitHub Copilot as the first partner — now extends to Cursor, with Atlassian listing additional partners including Figma, Canva, Replit, and Lovable. The common thread is Atlassian's Rovo MCP server, which provides a single authenticated connection to Jira and Confluence for compatible AI clients.
For teams already using Cursor for day-to-day development, this integration closes a meaningful workflow gap: tickets no longer need to be manually translated into agent prompts. The assignment itself becomes the instruction.