nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Rovo MCP in ChatGPT: same account across separate Jira and Bitbucket organizations?

Jk Mu

I'm trying to use the official Atlassian plugin in ChatGPT for Jira, Confluence, and Bitbucket PRs with one Atlassian identity.

Jira and Confluence are in organization A, while the Bitbucket workspace is in organization B. The existing Jira/Confluence connection works, and both organizations allow the Bitbucket read/write MCP toolsets.

During OAuth, selecting the Jira site disables the Bitbucket workspace with: "No workspaces from the same organization as the selected site are available."

I then tried Settings > Connected accounts > Connect another account in the official plugin, using the same Atlassian identity. I left Site empty, selected only the Bitbucket workspace, and selected read_bitbucket and write_bitbucket, with search_code unchecked (2 of 3 permissions). After accepting, ChatGPT returned: "This account is already connected."

After refreshing, only the original connection remains. A read-only Jira test still works, but direct Bitbucket PR operations are not available through the official plugin. I can't confirm which scopes the active connection retained. This was reproduced on October 23, 2026, with plugin version 2.0.2.

Is there a supported way to connect Jira/Confluence and Bitbucket across separate organizations using the same Atlassian identity in ChatGPT? Are separate connections supported for that identity, or is a different setup required? I'd like to preserve the working Jira/Confluence connection without transferring organizations or enabling code indexing.

I'm not sure whether this is a client limitation, an authorization constraint, or a bug. Guidance on the supported setup would help.

Comments

Jemma Swaak

Hi @Jk Mu,

Thanks for the detailed write-up.

The disabled Bitbucket workspace is intentional. The Atlassian MCP server limits each authorization to a single organization, so selecting the Jira site in org A only offers resources from org A. We set this boundary on purpose to protect each organization’s data, and one connection can’t span two organizations.

The “already connected” message follows from the same limit. The plugin allows one connection per Atlassian identity. Your identity is already connected to Jira/Confluence in org A, so you’d have to disconnect it before connecting to Bitbucket in org B. We know that’s not an ideal experience when you need both.

I’d like to walk through this with you on a short call to look at your setup and work out the right approach. Feel free to book a time that works for you.

Thanks again for raising this,
Jemma Swaak

Jk Mu

Hi Jemma, thanks for clarifying.

The underlying use case is coordinating development through an OpenAI Dot that delegates work to Codex chats. In our setup, those delegated chats can use globally installed plugins, but cannot access our locally configured Bitbucket MCP server. That led us to the official Atlassian/Rovo plugin.

We need the delegated chats to access Jira issues, Confluence documentation, and Bitbucket pull requests together. The same Atlassian identity has access to all three, but Jira/Confluence and Bitbucket are in separate organizations.

We understand the organization security boundary. The missing capability is having two independently authorized, organization-scoped connections active simultaneously under the same identity. Each connection could retain its existing organization boundary.

Disconnecting Jira/Confluence to connect Bitbucket prevents that workflow. Consolidating organizations also appears blocked by BCLOUD-23320; creating a replacement workspace and migrating repositories would involve changes to permissions and development integrations.

Is there a supported way to maintain both connections, or could this be considered as a feature request? It would also help to understand whether the one-connection restriction belongs to the Atlassian MCP service or the ChatGPT plugin integration.