Calling on all workspace Admins - Connect your Bitbucket workspace to an Atlassian organization

[Josh]

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:

[AX-472] Support migration/organisation consolidation of larger organisations into the new user management experience

[Yana]

Hi @Josh 

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. 

Cheers 

[vasanth]

we can easily manage all app's at one place

[s_mokhov]

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.

[s_mokhov]

Can an org contain other orgs as sub-orgs?

[George Nacouzi]

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. 

[Yana]

@s_mokhov 

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. 

[Yana]

@s_mokhov 

An Org will offer business units in the near future with ability to separate user directory and Atlassian apps within each unit.

However an org will always be the top hierarchical level and is one entity, there are no sub-orgs. 

[Yana]

@George Nacouzi 

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. 

[Jason Latona]

I find it par for the course that the screen caps don't appear to align with the interface I see at admin.atlassian.com lol

[尾崎祐真]

Hi @Yana 

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?

Thank you for your clarification.

[Jonathon Choy]

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?

[Yana]

@尾崎祐真 

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. 

Cheers

[Yana]

@Jonathon Choy 

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.