The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Merge and rename of Workspace

Peter Bysøe
November 20, 2023

Hi Atlassian,

 

We own 2 workspaces (Lets just call them workspace A and B for simplicity) and want to merge them together and rename. So what we want is:

  1. Merge workspace A into B
  2. Delete workspace A
  3. Rename workspace B into A

The reason for doing it this way around is that we want the name from workspace A but have a ton of repos and automation set up on workspace B that we don't want to mess with.

So the question is if there are are complications with this? Fx could the workspace A name still be reserved after deletion, so we can't use it?

 

Regards

Peter

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Ben
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 21, 2023

Hi Peter,

As per our documentation, it will take 30 days to completely delete an account, meaning that if you deleted WorkspaceA, its WorkspaceID (name) would not be available for 30 days. Additionally, it is not possible to merge two workspaces together and instead, you must transfer the repositories from WorkspaceA to WorkspaceB.

The best method for achieving what you wish to do is as follows:

1. Transfer all repositories first from WorkspaceA to WorkspaceB so that WorkspaceB has the data you want

2. Change the workspaceID for WorkspaceA so that the ID you want is free for usage

3. Change the workspaceID for WorkspaceB to the previous ID for WorkspaceA

4. Delete WorkspaceA

This would be the best method as you would not need to wait 30 days for the workspaceID to be free and you would also not need to update your GIT config to reflect the new remote URLs for your repositories (as with the workspaceID change, these would be the same as before).

NOTE: We do have a script to handle bulk repository transfer. Please have your admin check the script to determine its suitability, as it is not developed by or officially supported by Atlassian:

Hope this helps, please let me know if any issues.

Cheers!

- Ben (Bitbucket Cloud Support)

DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events