Summary

When a user has access to multiple Atlassian organizations, the app switcher (grid icon, top-left) allows filtering by organization. For Jira and Confluence, selecting an organization correctly narrows the product links to the sites belonging to that org. However, Bitbucket ignores the organization filter entirely — clicking the Bitbucket link always redirects to the user's default Bitbucket workspace, regardless of which organization is selected.

This causes confusion for users who belong to multiple organizations, each with a different linked Bitbucket workspace. The expected behavior is that selecting an organization should take the user to the Bitbucket workspace associated with that organization.

Steps to Reproduce

1. Log in to any Atlassian product with a user account that belongs to two or more organizations, each with a linked Bitbucket workspace
2. Open the app switcher (grid icon, top-left corner)
3. Select Organization A from the left-hand org list
4. Click the Bitbucket link
5. Note which workspace loads
6. Repeat steps 2–4 selecting Organization B instead
7. Note that the same workspace loads in both cases

Expected Behavior

When Organization A is selected in the app switcher, clicking the Bitbucket link should navigate to the Bitbucket workspace linked to Organization A. When Organization B is selected, it should navigate to Organization B's linked workspace.

Actual Behavior

The Bitbucket link always navigates to the user's default Bitbucket workspace regardless of which organization is selected in the app switcher.

Why This Is Now a Gap (Not Just a Limitation)

This behavior was previously documented as expected because Bitbucket was classified as a "tenantless" product with no formal workspace-to-organization relationship. However, as of March 2026, all paid Bitbucket workspaces are required to be linked to an Atlassian organization, and auto-linking was applied to any remaining unlinked workspaces. The workspace-to-org relationship now exists in the platform, but the app switcher has not been updated to consume it when routing Bitbucket links.

The app switcher's own announcement (March 2024) explicitly noted that org filtering for Bitbucket was not supported "yet", implying intent to support it in the future.

Impact

Users in multi-org environments are unable to navigate to the correct Bitbucket workspace via the app switcher. This results in:

• Confusion and friction when switching between organizations
• Users getting stuck on the wrong workspace with session/cookie issues requiring manual clearing
• The app switcher org filter feeling broken for Bitbucket users

Workaround

Users must navigate directly to https://bitbucket.org/<workspace-slug> or use Bitbucket's own avatar menu → Switch workspace.

Related

• https://jira.atlassian.com/browse/BCLOUD-23320 — Transfer Bitbucket workspaces between organizations