Yana Atlassian Team

@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…

@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.…

@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.…

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…

@Jessica Rodrigues Yes, Bitbucket is migrating to Atlassian billing experience, that will allow Billing Admins to see billing from Atlassian Administration. Here is the help document for the new billing experience that Bitbucket is joining:…

@ollie jones Thank you for the feedback. Our goal was not to create confusion, but to emphasize that linking your Bitbucket workspace to an Atlassian Org is a critical first step that needs to happen before we can enable centralized billing and user management for these workspaces. It is not going to happen immediately…

Hi @Eric Gruss Thank you for your question ! By linking your Bitbucket workspace to Atlassian Org, you are not changing product access or permissions. This is not a migration, this is a first step that is required for migration Also, once your Bitbucket user management transitions to Atlassian Administration, you will be…

@Alex Brousseau Thank you for reporting, our team is looking into correcting this behavior, apologies for the inconvenience. Is there a specific reason that is preventing you from linking your workspace at this time ? If you need help, our team is happy to help and walk you through the process, it will take less than 3…

@Tomasz Poradowski Apologies for the behavior, the popup is dismissible, however it will come back within the next 24 hours unless you link your workspace. Once the workspace is linked, you just need to refresh your browser with Bitbucket session and the popup will be cleared. We appreciate your partnership in linking your…

@Mat I see that you were able to accomplish the Org creation and linked your workspace, thank you for doing that, we really appreciate it. I have shared your feedback with out team responsible for intake in support portal, thank you for your candid feedback!

@Ginger In your Atlassian Administration, when you navigate to Apps and if you see your workspace on the list , it means the link was successfully established. The option to Link Bitbucket workspace will always remain available, because you can link multiple workspaces to a single Org. If you need additional help, please…

@Mat To help troubleshoot the email notification issue, please reach out to our support team for help, by raising a ticket here https://support.atlassian.com/contact/#/?inquiry_category=technical_issues&product_key=cloud-administration&is_cloud=true&support_type=customer please make sure you specify that you are not…

@Shelby C Linking your workspace to an Atlassian Org will have no impact on any of the existing functionality. If your organization has Atlassian Guard subscription, you will benefit from having Audit logs for Bitbucket app captured in Atlassian administration post linking. Your team will only experience changes once we…

@Mat Hi Mat, Once you create a new Atlassian Org, you will just need to link Bitbucket workspace to that org, we will take care of the rest for you during migration! No need to type any user emails manually. If you are interested in our EAP program to migrate your users to Atlassian Administration, please fill out this…

@Mat Hi there, Creating an Atlassian Org is free and you do not pay for users in the Org. That might have been for a Guard subscription, which your team gets a free trial of for 30 days and you do not have to signup for it after the trial runs out. To learn more about an Atlassian Org please refer to…

@Gen Hi there and appreciate your questions. Here are the answers: Does linking require that Bitbucket workspace admins also become Organization admins? If so, there is a concern that Bitbucket workspace administrators might be granted excessive privileges—such as permissions to configure organization-wide security…

@Dave Biddle You do not require a payment method to try our product. Once the trial runs out, and you do not wish to use the product, you'll just lose the features that Guard offers. It will not have an impact on your Bitbucket operation or workflows. 

@Joe Lupfer Hi there, By linking your workspace to an Atlassian org, you will not lose the ability to manage users in Bitbucket and at this time everything will remain the same. However by taking this fist and critical step you are: 1. Creating a map to allow our team to then migrate your users and group to this Org that…

Hi @EC Linking your workspace to Atlassian organization is completely Free, you do not need to pay anything extra. Signing up for an Atlassian org for your company, if you do not already have one, is also free and doesn't require a payment method. Please reach out to our Support team if you need help with any of the steps…

@jarney Bitbucket billing doesn't change with either linking of the workspace or migrating users to Atlassian Administration. Each user is billed based on product access and license they consume within each workspace. If you have 2 separate workspaces right now, they are billed separately and linking both to the same…

@bcrabb Authentication via SSO is done through Atlassian account, so this applies to all users regardless of product access. However product access and groups synching with your AD provider will not yet be supported with this initial step of linking your Bitbucket workspace with Atlassian Org. As a followup step, our team…

@Marco Cornelio Thank you for your question, I have updated my post to add an FAQ, that should help answer your question. Thank you 

@Daniel SHEN I'm sorry to hear that you linked your Bitbucket workspace to a wrong Atlassian Organization. let me ask our Support team to help you get untangled and get you on the right track. Please look out for a ticket from us. Thank you

@Daniel SHEN When you access your Atlassian Org from admin.atlassian.com > Navigate to Apps or Products on the horizontal navigation menu and you should see a "..." per screen shot below. Hope this helps clarify. Thank you.

@caseyamcl there are no changes to workspaces that are on Academic or Community plans. Those workspace are not impacted by this change. Atlassian is dedicated to supporting those organizations and this change doesn't affect them. Thank you

Hi @Michelle McGinnis For SourceTree specifically, we have also added instructions to our public FAQ, depending on the version you are using MacOS or WIN. Here is the link to the FAQ on how to update your known_hosts file for SourceTree:…

Hi @Rock Thank you for raising your question. With new Branch view page and Diff is actually shown automatically and you can configure in Settings if you would like to see a "Unified' view or a "Side-by-side" view of the files that have changed. Please see screen shots: Additionally, if you go to Branches > select "... "…

@Sravya Dega That is correct, there should be no impact to your repositories at all. 

@Sravya Dega Leaving Services until we remove them for you will not affect anything for your and your team. Those will be removed automatically by our team and all integrations that are using Services will stop working as of December 31. For any integration you would like to add or make sure that the integration continues…

@Pim Apologies that the API call didn't return any data for you. I'm going to reach out to you directly on the ticket and share with you the list of repositories that are going to be affected by this deprecation. Thank you for working with us through this.