Video wird geladen...
Video konnte nicht geladen werden
Cursor is now available in Jira. Assign Cursor to work items, or mention @Cursor in a comment to kick off a cloud agent. Cursor uses the title, description, comments, and your team's repository settings to create a merge-ready PR.
263,209 Aufrufe • vor 4 Monaten •via X (Twitter)
35 Kommentare

You can ask Cursor to fix bugs, add features, update tests, or investigate a task described in the work item. Learn more:

Composer 2.5 is super tempting

This might single-handedly save Atlassian

This is a huge workflow upgrade for dev teams ⚡ Turning Jira tickets directly into merge-ready PRs with Cursor could save hours of context switching and manual setup.

Jira 🤝 Cursor

The interesting part isn't Jira itself, it's that the work item becomes executable. But title + description + comments + repo settings still isn't enough unless the ticket also carries acceptance checks and an escalation owner. Otherwise you get PRs that look merge-ready and are operationally wrong

When Jira tickets start launching agents, cost visibility has to ship with them. We support Cursor in Alephant so teams can see what each coding session is costing: token usage, model spend, alerts, and a live dashboard for every run. Free + open source

Mentioning @cursor_ai in a Jira comment to kick off a cloud agent is the workflow integration that makes this feel real — it meets the team where they already work instead of requiring a context switch. The "work item → merge-ready PR" loop is exactly what async engineering teams need.

repo scoping is where these usually get weird. if that part stays clean, jira could be a legit front door for agent work.

Much needed integration, thanks cursor team! Pushing even more after composer 2.5

It's so close, just needs Bitbucket support to make it work in the Atlassian stack

This is a game changer!

Add linear and I’ll leave Claude code

Cool

wow

@aradcliff0

Finally

I hate that I need this (Jira)

Does this work with your Cursor billing or through Atlassian (Rovo) credits?

@shaoruu Why Jira with cursor? Just use the hotkeys

insane integration

This is the stuff I have been talking about! Just wait and see what we end up doing with this! Huge win! Massive Congratulations to the teams involved that made this successful and happen!

we do need cursor app .web edition really sucks

@tibor_tee Can’t believe cursor were the ones to fix jira

Perhaps improve your customer service agents (bots), they're useless and hallucinate. How can a business of this size miss this?

Game changing

builders keep making tomorrow look obvious five minutes after it ships

Cloud agents still use max mode only? Kinda impossible for me to use it in the current state

The jump from code editor to Jira integration is huge. Cursor is becoming infrastructure at this point

Better than Rovo hahaha

Finally, agents doing the Jira dance for us.

Tidal wave of tiles being created rn

Is Jira becoming the new control panel for AI-driven software development? Are we heading toward SDD (Spec-Driven Development), where humans write specs and agents ship the code?

GET READY!

The real unlock is not “AI writes code from Jira.” It is whether the agent can preserve product intent, repo conventions, edge cases, and review discipline while moving from issue to PR.

