Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
Hi @Yana . It was nice speaking with you back in August.
Have there been any updates on the timeline for larger orgs with the older user management configuration? This JAC ticket hasn't seen any public-facing comments since it was created:
The team is working with EAP customers first half of the year and plans to go GA in the second half.
With that being said, I can see that your Bitbucket workspace is not yet linked to an Atlassian organization of your choice, I would still highly encourage you to do so.
If you would like for your workspace and Org to be included in the EAP, please send me a message to let me know and we will take it from there.
Yikes... I have dozens of academic workspaces I created for different groups in courses I've been teaching, so I am going to have dozens of orgs now, wonderful. And there were movement and forks of repos between the workspaces... I foresee a mess come March 15. Not a welcome change, just like disabling cross-workspace forks. Used to love bitbucket and Atlassian over GitHub on many levels, and this is dissipating now.
what happens if my BB account has a different email than my official Atlassian account? i have 2 emails and i have Atlassian accounts on both. I need BB to be linked to the second Atlassian account not the first, and i am not able to change the email because an Atlassian account exists on the second one as well.
My recommendation would be to reduce the number of workspaces you have created in BB and then link workspaces you would like to keep to a single Atlassian Org. I would definitely advise not to wait until March 15 and do that as soon as possible to not end up with multiple orgs.
That will help you later manage groups' access to each Bitbucket workspaces in Atlassian Administration and add/remove users from a single place across multiple workspaces without having a need to go to each workspace separately.
For the Forking functionality, your students will be able to create their own fork within the same workspace and still do their independent work and submit a PR to the parent repo afterwards.
I would recommend reaching out to our Support team to help you consolidate all access under a single identity and single email address, if that is what you are looking to do.
Talking to support team to help them understand your end goal, they will then be able to provide you with the next best steps to achieve your goal.
We have a question regarding IP Allowlisting settings during the workspace linking process.
**Question:** Will our existing IP Allowlisting configuration be preserved after linking our Bitbucket workspace to an Atlassian Organization?
We currently use IP Allowlisting (Premium feature) to restrict access to our repositories, and we need to ensure this security setting remains intact throughout the migration process.
Could you please confirm whether: 1. IP Allowlisting settings will be automatically preserved during the linking? 2. Any action is required from our side to maintain these settings?
Late to the party here, having linked a single workspace to one org there doesn't appear to be any immediate differences ie not seeing the org group name fall under the Bitbucket icon in the switcher menu. And with 3 separate orgs and multiple bitbucket workspaces how does this make it simpler?
Bitbucket IP Allowlisting will not be impacted during Org linking, or any subsequent migration stages. All Bitbucket features including code collaboration is not going to change.
Linking your workspace to an Atlassian org is the first step, this creates a map for our team for future migrations that will soon follow, including new Billing platform and Centralized user management.
By linking your workspace to an Org, will not have any immediate impact.
If you have multiple workspaces that should be managed from a single AD, you should link them all to a single Organization, that will provide you with apps and users visibility and ability to manage all your users and their access across all Atlassian apps in a single place.
We have been trying to link our bitbucket workspace to our atlassian org since November, but the bitbucket workspace is still missing from the select workspace page.
The AI support bot says that the workspace is not eligible yet, but there is only 10 days left before the deadline, and I wonder when it will be eligible...
I have reviewed your current workspace and it is not yet eligible to be linked to an Atlassian org.
We will notify you via email when it becomes eligible. The current deadline is only applicable to eligible workspaces. Appreciate you checking though! We will be in touch with the next steps for you as soon as your workspace becomes eligible.
@yana My local bitbucket workspace admin did not reach me out (Atlassian Organisation Admin) and created a new organization and linked his workspace to this new one. Can we still link his workspace to our company Atlassian organization?
Atlassian Team members are employees working across the company in a wide variety of roles.
March 6, 2026 edited
@Maximilian Floß please reach out to our support team and share your Bitbucket workspaceID and desired Org ID. Support will evaluate and let you know if this is still possible.
We have successfully completed the step to link our Bitbucket workspace to our Atlassian Organization. From our observation, it seems that this step only mapped the workspace to the organization, and the actual migration to centralized user management has not taken place yet. Could you please help clarify whether there is an estimated timeline or scheduled date for when the actual migration will occur? Additionally, please let us know if there are any further preparations required from our side before the migration is executed.
Thank you for taking this step, your observation is correct, we haven't migrated your workspace to the centralized user management , however I can see that your workspace has already been migrated to our new Billing system!
Centralized user management is the next step and this will be happening in the Summer and Fall of this year. I'll be posting an additional community post and we will email all workspace admins to notify them when the migration is coming and how to prepare.
Atlassian Team members are employees working across the company in a wide variety of roles.
March 11, 2026 edited
@s_mokhov apologies, this is a current limitation, big majority of our customers do not have more than 5 workspaces, however I can see in your case this is different. Have you considered consolidating some/all of your workspaces under 1 ?
124 comments