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