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

[Yana]

Hi @Matt Chamlee @Alexander Khalilov 

Thank you for reporting the issue, the flag wasn't intended to cover any parts of the UI navigation but serve as a reminder, apologies. 

Our team has temporarily turned it off while we look into correcting this behavior.  You should not see it after a refresh.

The flag and the UI modal are only shown to workspace Admins, since those are the users that can perform the linking of the workspace to an Atlassian Org. 

[Alexander Khalilov]

Hello, @Yana 

Two days ago we had discussion about new reminder window on UI, and that it covers some navigation parts.
You confirmed, that it will be turned-off.
Today I'm seeing this window again, on the same place without any changes (like buttons "remind me  later", "dismiss" etc)

 
I just would like to know, what a hell Atlassian is doing?

[Matt Chamlee]

@Yana Same for me, the pop-up appears to be back as of a few minutes ago (I don't recall seeing it earlier in the day).

[David Moser]

Hi, @Yana

I have been following this thread and have a few concerns. We have different Bitbucket workspaces for different purposes. For most of those workspaces, we only have internal company users: thus, no issue linking such workspaces. However, another purpose is to have secure Bitbucket workspaces where we can have customers access secure code repositories for their specific custom integrations. We obviously do not and cannot have those users be part of our central SSO user authentication flow.

How do you propose we handle such workspaces where we have external customer users that should not be authenticating via our SSO user authentication flow?

[Yana]

@David Moser 

Thank you for your question.  The external user policy would apply to Bitbucket through Atlassian Guard as described in 

https://support.atlassian.com/security-and-access-policies/docs/what-is-external-user-security/

Our team has created a Feature request to support this functionality with Bitbucket App as well. 

Please follow and vote for this feature: 

https://jira.atlassian.com/browse/ACCESS-2124

With that being said, in your current situation, you have 2 options: 

1. Link workspace with external users to your existing Org, this will help bring billing into single view but we will not yet migrate your Bitbucket users to Atlassian Administration until the feature above is implemented 

2. Create a separate Atlassian Org, that you would use specifically only for workspaces you manage with external users. I'm not sure though if this would meet your company's needs. 

I would recommend reaching out to our Support team to explain your requirements in detail and this will allow us to review your current setup and offer the best path forward for you. 

Thank you

[Rexhaj Liridon_ BKW]

Will we be able to ignore this indefinitely and never link it to an Atlassian organization? Jira and Confluence are managed by our corporate IT, while we are the only team using Bitbucket. Linking it to the Atlassian organization would require them to set up an entirely new service on their side, and we would inevitably lose some of our rights. This would be very troublesome for us and generate high costs.

[Jorge Miranda]

Hello! Honestly, in our case, we only use Bitbucket as a repository, and I don't see the need for this change. But from what I see, will the change ultimately be mandatory?

[Andy Mell]

I’m sick and tired of Atlassian forcing unwanted changes and behaviours on our users. You made a mess of Jira and confluence by adding more options and confusing UX now you’re doing the same with bitbucket. I don’t want to migrate, I’m done with you guys.

[Alexander Khalilov]

Does anyone understood how this changes affect monthly cost of usage current plan?
I don't understand why the topic doesn't contain any information about the cost of "linking" and the cost of features provided. It's still the feeling, that such aggressive offer, hide some extra payments or price increase (sure without to roll back this "linking") 

[Yana]

@Rexhaj Liridon_ BKW  @Jorge Miranda @Andy Mell  @Alexander Khalilov 

Hi there, 

• Having Bitbucket join Atlassian Administration and give ability for Admins to manage all Atlassian Apps and users/groups and billing from a single place is one of the most requested features and our team has worked hard to make this a reality.  We are asking for partnership from workspace Admins to link their workspace to an Atlassian Org, to provide a map for our teams as to,  in which Org Admins want to see all their Apps, users, groups and billing to help streamline user management and remove the overhead of having to manage them in multiple places.
• Linking your workspace to an Atlassian Org is a required step that we are asking Admins to take to create the mapping. 
• There is no additional cost associated with this step, your billing and licensing is not changing for Bitbucket product. Signing up for Atlassian Guard is optional, and if you do decide to signup for it, the cost will be associated with a new subscription, your Bitbucket subscription is not changing unless you add/remove users. 
• UI navigation in BB is not changing,  and by linking your Workspace to an Org will not have an immediate effect on user management.  Our team will share additional communication when we are migrating your users/groups to Atlassian Administration and your workspace to a new billing engine for centralized billing management. You can learn more about the new billing experience by reading this Community post .

If you have any additional questions specific to your situation, please reach out to our Support team and they will be able to review your case and provide best possible advise based on your use case. 

Thank you

[David Boreham]

This seems to be quite the s.show.

I received emails telling me that I need to link our bitbucket repos to an atlassian org.
Ok fair enough. But the email spends 99% of its content telling me why it's a great thing
that the user management is being consolidated. Needless noise to the intended audience:
people who manage software repositories -- so they're all familiar with user management
already. But what the email does not say is HOW I am to do this linking. Ok I think perhaps
it's intuitive. So I log in. Nope, I immediately get lost and end up dumped into a generic
Atlassian home page. I go on vacation. While on vacation I get another more shrill email.
Same stuff about why this is so great. So I interrupt my vacation to see if I can do this linking
thing, since continued repo access is mission critical to my company. Check in the email
for some sort of doc, screen shots, etc. What I find is a link to this thread.

Come one people --- walk through the migration process yourself with a test repo and org.
Take some screen shots as you go.
Have Chat-GPT make a doc page with said screen shots.

[zachary_laraman]

This mirrors my experience. There is no shortage of cult-like droning on about how it promises world peace, an end to hunger and path to enlightenment. Nowhere though is there any comprehensive information about HOW to do it. Just increasingly aggressive messaging which is now quite clearly saying, you MUST do it. In short, tasks are being deligated to paying users.

[Yana]

@David Boreham @zachary_laraman  Hi there. 

Thank you for your feedback. The details you are looking for were included in the very first email we sent and not to repeat it every time, the detailed instructions are posted on this community post, here they are: 

Please follow the steps in Add a new Atlassian app to your organization | Atlassian Support or use the instructions below to link your Bitbucket workspace to an Atlassian organization.

If you are a Bitbucket workspace admin and an Atlassian organization admin

1. Go to admin.atlassian.com.

2. Select the organization you would want to link your workspace to. (Note: Please only select the workspaces that you want to be part of your organization as you will not be able unlink them later.)

3. On the top navigation bar, select Apps.

4. In the upper-right corner, select … and then select Link Bitbucket from the dropdown menu.

5. Follow the prompts and pay close attention to any messages provided or actions you may need to take. 

6. Select the workspace you want to link to your Atlassian organization. Note: You can only link one workspace at a time.

7. Confirm that this is the workspace you would want to link and give the process some time to complete.

8. Refresh the Apps view to see the newly added workspace on the list of available apps.

Please let me know if this helps ? 

[Fei Yan]

When I click link I can see the workspace, but after I select the workspace, the next button is still greyed out.

[Yana]

@Fei Yan 

I have looked into your account, everything seems fine configuration wise and I do not see any blockers.  Please raise a ticket with our support team to help  with going through the steps. When raising a ticket you can mention this thread. Thank you

[David Moser]

Just in case this can help anyone, I am posting a screenshot showing you where to click in what order to get to the screen to link a bitbucket workspace to your organization from the Org Administration Page. 

[David Boreham]

For anyone arriving here who is still confused here's what they did to confuse you:

1. The magic linking can only be done from a UI area in the Atlassian site that deals with "organization administration". If you're a bitbucket admin but don't mess with Jira/other Atlassian stuff you never saw this UI before and you will probably not know how to navigate to it from the Atlassian home landing page. Easiest to get to it via: admin.atlassian.com (which tbf the instructions to say but easy to not spot that and type www.atlassian.com instead which will get you lost).
2. Having arrived there you need to get it into an "apps" admin mode which is fairly obvious and clear in the instructions.
3. Then: you need to know that the next thing to click is literally an area of the screen to the right of an "Add app" button. It's a button that is very light grey on a white background and has the text label "..." (yes literally three dots). The instructions include this but are unparsable by any reasonable reader because it just looks like they're adding ellipsis to the narrative about what to click like ... this. There are now some screen shots that show this but until you see it live it doesn't really click what's going on.
4. Once you click the nearly invisible secret three dot button it pops up a menu that includes "Link Bitbucket" and you're off and running.

Hope this helps.

[Mikko Pukki]

It seems that Rovo will be enabled by default and Atlassian AI cannot be disabled for bitbucket before linking it to the organization, as there is no global flag for disabling AI, but it is a product specific setting? So can there be a time period when AI capabilities are forced to be enabled? Because we cannot let them be on. My understanding is that OpenAI handles the data in US. We cannot let any data be processed outside of EU. If the AI options are enabled even for a short period we are forced to change the product for something self hosted.

[PeterW]

This was a mess. No instructions for a month, then instructions that don't actually work (there's no Atlassian Apps link, at least not for us).  Getting redirected about 700 times to make this comment was nice too.  I just wanted to make a PR!

[Yana]

Hi @Mikko Pukki 

Thank you for your question. Completely understand your concern and happy to put you at ease. 

In Bitbucket workspace settings, you can disable Atlassian Intelligence (AI) by following the steps outlined in this help document.  Once the AI is disabled at the product level no Bitbucket data will be indexed by AI, you can proceed with linking your workspace. The product setting will be respected even if AI is enabled for other products within the same Atlassian org and will not be turned back on unless you, as a workspace Admin enable it from the workspace settings. 

Rovo Chat will only be available within Bitbucket when:

1. Atlassian Intelligence is enabled in Bitbucket workspace settings  and
2. You integrate your Bitbucket workspace with your Jira site that also has Atlassian Intelligence enabled.

This means that as the Admin you have full control over AI enablement.