Cursor AI Updates: May 20, 2026

1. Cursor adds a Jira integration that lets you assign tickets directly to a cloud agent

Cursor. The May 19 changelog entry introduces a first-party Jira integration that turns work items into cloud-agent tasks: assigning a Jira ticket to Cursor (or mentioning @Cursor in a comment) kicks off an agent that reads the title, description, comments, and configured repository to scope the work, then handles bug fixes, feature additions, test updates, or investigations. When the agent finishes, the Jira ticket is updated with a pull request link so reviewers can jump straight from the issue to the diff, keeping the audit trail inside Atlassian. Source

2. The Jira hook-up requires Rovo and admin access, narrowing the rollout to Commercial Cloud teams

Cursor. Enabling the integration is gated on two things: Cursor admin access on the workspace side, and a Jira Commercial Cloud tenant with Atlassian’s Rovo AI layer turned on. That excludes Jira Server, Data Center, and free Cloud tiers from the launch, and effectively ties Cursor’s agent-in-Jira flow to teams that have already opted into Atlassian’s paid AI surface. Installation runs through Cursor’s integrations dashboard with per-environment repository mapping, so the same Jira project can be wired to different cloud-agent environments depending on which codebase the ticket touches. Source