Jira Cloud Agent resolves Bitbucket default repo as github.com

[Graham_Mackenzie]

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

[Colin]

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

Originally, even this workaround wasn’t possible.

@Graham_Mackenzie

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

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.

[Nick_XPV (Nick)]

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.