Jira Cloud Agent resolves Bitbucket default repo as github.com

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Bitbucket-only team (no GitHub). Jira + Bitbucket connected. Require individual authentication enabled. Under Cloud Agents → My Settings, Default repository and Routing Rules are set via the Bitbucket dropdown (not free text) to our Bitbucket repo.

Triggering from Jira/Rovo without an explicit repo= fails: error cites a github.com URL for WORKSPACE/REPO and asks to update the GitHub connection / install the Cursor GitHub App.

Explicit full Bitbucket URL in repo= works and starts the Cloud Agent correctly.

So the dropdown selection is Bitbucket, but the Jira kickoff path rewrites it to GitHub.

Related: same GitHub-fallback class of bug for GitLab + Jira (forum topic: “Jira App Integration Not Creating Cloud Agents with Gitlab Repository”).

Steps to Reproduce

  1. Connect Bitbucket only (no GitHub).
  2. Enable Jira individual authentication.
  3. Set My Settings default repo (and optionally Routing Rules) from the Bitbucket dropdown.
  4. From Jira/Rovo, ask Cursor to work a ticket with no repo= parameter.
  5. Observe error citing a GitHub URL for WORKSPACE/REPO and asking to connect/update GitHub.

Expected Behavior

Jira kickoff should use the Bitbucket repo selected as the default / routing-rule target (Bitbucket Cloud host + WORKSPACE/REPO), not rewrite it to GitHub.

Operating System

MacOS

Version Information

Jira App Integration + Cursor Dashboard (web). Bitbucket Cloud integration (public beta).

Additional Information

Workaround: always pass repo=hxtps://bitbucket.org// in the Jira/Rovo trigger. Short form repo=/ appears to hit the same GitHub assumption.

Default repo / routing rule UI only offers a Bitbucket dropdown (no free-text URL), so we cannot force the bitbucket.org host in settings — only via the explicit repo= URL in the trigger.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Thanks for reporting this, @Graham_Mackenzie! We’re seeing this issue with both Bitbucket and GitLab.

Originally, even this workaround wasn’t possible.

Now it is, but we should still improve the experience so that the workaround isn’t necessary. We have an internal issue tracking this, and I’ve attached your report to it.

We are seeing the same issue (please see a screenshot below). A couple of notes:

  • Bitbucket is connected.
  • The default repository is set on the team-level settings. The routing rules are also set to our Bitbucket repo.
  • Despite all of that, Cursor in Jira defaults to GitHub.

Hey @Graham_Mackenzie,

Thanks for the report. The Jira kickoff rewriting your Bitbucket default repo to a GitHub URL has been addressed on our side and will be rolled out soon if it hasn’t been already.

Could you give it another try from Jira without the explicit repo= parameter and let me know if it still points at a GitHub URL?

cc @Nick_XPV

Hello @Colin

I am still experiencing the issue described by @Nick_XPV above.

Notably I’m setting a different repository than the Team Default. The owner and name i set are respected, but it is otherwise still saying no access to GitHub instead of the BitBucket repository I have set.

Would appreciate any assistance.

Thanks,

Ryan

Hey @ryanjfar, thanks for the details.

The change we mentioned above is live, but we found one remaining case. When a Bitbucket repo is named only as workspace/repo (in a routing rule, a default, or a short repo= value), it can still be sent to GitHub. Whether you hit it depends on which repositories your own connected Bitbucket account returns to Cursor, so it can work for one teammate and fail for another on the same team. I’ve passed this along to the team.

In the meantime, this should get you unblocked:

  1. In the Jira comment, use the full repository URL instead of workspace/repo, for example: repo=https://bitbucket.org//
  2. In the Cursor dashboard, open Integrations and check that Bitbucket shows as connected for you, and that the Bitbucket account you connected can open that repository in Bitbucket. If it can’t, disconnect and reconnect Bitbucket with the account that has access.

Two quick questions so we can check this on our side:

  1. Does your team have “Require individual authentication” turned on in the Jira integration settings? If it’s off, the full URL will come back with a message that Bitbucket isn’t enabled for Jira yet. Turning that setting on (each person then links their own Cursor account and Bitbucket connection) is the way to use Bitbucket from Jira today.
  2. What email do you use to sign in to Cursor?