Issue connecting Jira with cloud agents

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Issue connecting Jira with cloud agents. The org admin tries to enable Jira, is being redirected to Jira where is being asked to install a cursor plugin in Jira, after doing so the Cursor Configuration in Jira states: “Your Jira site is linked to Cursor. Users can assign issues to Cursor or @mention it in comments to launch cloud agents.”

A button bellow for “Manage Settings” takes the admin to Cursor https://cursor.com/settings/jira which gives a 404

Users within Cursor are still unable to manage and connect to Jira through “https://cursor.com/dashboard/integrations” the option is disabled.

Expected to be able to use Jira integration for Cloud Agents and users of the organization to be able to connect to Jira using OAuth

Steps to Reproduce

Have an org with restricted MCP management
Ask an admin to enable Jira integration through https://cursor.com/dashboard/integrations
Admin will be redirected to Jira and asked to install Cursor plugin in Jira
After installation try to follow the CTA - Will give a 404
Users in org are still unable to connect using OAuth to Jira through integrations, the option is disabled

Operating System

Other

Version Information

It’s all in web configuration. No specific Cursor version or OS

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

7

Hey @Dimitris_K,

The 404: the “Manage Settings” button points to an old address. A team admin can reach the Jira settings directly at https://cursor.com/dashboard/integrations?view=jira-management. That’s not intended behavior and it’s an issue we’re tracking.

The disabled option: connecting/managing Jira is admin-only, so it’s greyed out for regular members (members don’t connect Jira from cursor.com). It also looks like the Jira site got linked to a different Cursor team than the one you’re on, which happens when the admin who set it up belongs to more than one Cursor team with the same name. Your admin can fix it from Jira → Settings → Apps → Manage your apps → Cursor Configuration → Disconnect, then Connect to Cursor and pick your main team. If that’s tricky, email us at [email protected] and we’ll re-point it.

Setup reference: Jira integration docs