Assign Jira work items to Cursor

[#1]

We’re thrilled that Jira’s Cursor integration is now available. Give your Cursor coding agent all the context it needs from Jira.

In addition to accessing all your team’s context in Jira through the MCP, you can now assign work to Cursor via the UI, mention Cursor in comments to collaborate and get status updates, or trigger Cursor to kickoff work automatically through workflows.

When you assign work to Cursor:

• The agent picks up context from the work item

• Progress is visible right on the work item, so there's no need to check a separate tool

• You stay in control: Agent work is only visible to you until you choose to share it with your team

How to Get Started

Requirements

Before you install the Jira integration, make sure you have:

• Jira Commercial Cloud with Rovo enabled

• Admin access to the Jira site where you want to install the app

• Cursor admin access to the team you want to connect

• GitHub or GitLab connected to Cursor for repository access and pull requests

The Cursor Jira integration is not currently supported in Atlassian HIPAA or FedRAMP (including Government Cloud) instances.

Installation

• As a Cursor admin, go to Cursor integrations

• Click Connect next to Jira

• Continue to the Cursor app listing in the Atlassian Marketplace

• Click Get it now

• Select the Jira site where you want to install Cursor and click Review

• Review the app, then click Get it now

• After installation completes in Jira, click Configure on the modal that pops up on the lower lefthand side

  1. If you miss the pop-up, go to your Connected Apps under Administration, select the Cursor app, go to its Connections tab, and select Configure from the three dots (⋯) menu

• Connect the Jira site to your Cursor team

• Complete any remaining Cloud Agent setup in Cursor:

  1. Connect GitHub or GitLab if you haven't connected a repository provider yet

  2. Enable usage-based pricing

  3. Confirm privacy settings

  4. Choose a default repository, model, and base branch (under Cloud Agents settings in the Cursor Dashboard)

• Return to Jira and start using Cursor from a work item

For more information - check out cursors documentation here.

Have questions? Ideas for how you'd use agents in your workflows? Drop a comment below. We'd love to hear how you're planning to put your new AI teammates to work!

If you’re interested in shaping the future of agents in Jira or sharing any feedback to make Jira work better for you and your team, we’d love to hear.

Book a time to chat with the team 🗓️. We’re excited to hear what you think!

[Jason Krewson]

I'm actually right in the middle of setting this up right now. Awaiting approval to integrate Cursor and hoping that happens soon as this is going to be so helpful! 

[Suresh Sakhare]

We have self hosted gitlab instance how I can integrate my repo with cursor?

[Himanshu Singh]

@Suresh Sakhare Here's a guide from Cursor on how to integrate with GitLab Self-hosted instances. It requires a Cursor Teams or Enterprise plan. 

[Jonathan Berkey]

Really glad to see this becoming native. The context handoff from Jira to Cursor is the piece most teams are doing manually today and it's surprisingly high friction.

One thing I found while building Nmbly: the harder problem is actually the return trip. Getting context into Cursor is step one, but getting the work back into Jira without manual status updates, PR linking, and ticket cleanup is where the gap stays open. I built bi-directional sync so the ticket reflects what the agent actually did, not just what it was asked to do. Slack bug reports, investigation reports, PR creation all flow back into the ticket automatically.

Curious how Atlassian is thinking about the return sync direction as this integration matures.

here's a little demo of a bug workflow in Nmbly https://www.linkedin.com/posts/jberkey_new-demo-showing-some-of-the-new-bug-automation-ugcPost-7475711516260884480-6I0d/?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAEZWFUBz5HOLFsuHognTFr8-znyopTNO1s