So I received the email telling me that "Atlassian account is coming to Bitbucket next week!"
Already have an Atlassian account? No worries, we'll join your Bitbucket account to your Atlassian account.
I have a personal Bitbucket account in which I have various repos that I developed personally plus I am a member of my company's team and have access to my company's repos. I also have a JIRA account (cloud) for my company's projects. I am unclear if my JIRA account is already an Atlassian account or it will be converted/"joined" to one.
My question: Is this saying that my personal Bitbucket account and my corporate JIRA account need to be joined? What does that mean? If I leave my company could they block my account's access to my personal repos? I don't understand how using one account to access all the Atlassian services reconciles with personal and corporate accounts. Should I create a corporate Bitbucket account to access my company's repos and keep my personal account just for personal stuff (removed from the company's team)?
Thanks for your questions.
The Atlassian account upgrade only changes the way you log in to your existing Bitbucket account - it simply enables you to use one set of credentials to log in to multiple services.
Is this saying that my personal Bitbucket account and my corporate JIRA account need to be joined?
If you connect the same Atlassian account (and thus email address) to your Bitbucket and JIRA accounts, you'll be able to log in to both accounts using the same credentials. However, if you'd prefer to log into each account using different email addresses, you can have two Atlassian accounts. The upgrade process for each product allows you to choose an email address to associate with your existing account.
If I leave my company could they block my account's access to my personal repos?
Only the login process is changing; nothing is changing with regard to repository access.
Should I create a corporate Bitbucket account to access my company's repos and keep my personal account just for personal stuff (removed from the company's team)?
This is an option if you prefer. Check out the example under "What if we use different email addresses to log in to multiple Atlassian products?" on the Introducing Atlassian account page for more info.
Thanks. Do let me know if you have any more questions!
I didn't ask this important question and paid the price - my personal account was effectively hijacked by my work account. All my personal projects are hostage to work now. My lack of permissions has ruined my personal account- I can't create projects anymore. I am glad I am not a freelancer anymore, this would have been a major setback. But I probably would have been more vigilant.
Atlassian really goofed up in my opinion.
I'm sorry that you've had a poor experience as a result of the upgrade.
The upgrade does not affect permissions - it only changes which email/password you log in with, which you can still change if you like.
I'd love to chat with you a bit more about how we can clarify and remedy your situation; if you'd like to do that, shoot us an email at support at bitbucket dot org and reference this comment.
After I upgrade and join my Bitbucket and JIRA accounts using my corporate email address will I still be able to log in with my personal (non-primary) email address? If so then I think it is all OK - If I leave my company I will lose my corporate email address, my (corporate) JIRA account, membership of the corporate Bitbucket team and the Atlassian account I would use to log into both Bitbucket and Jira, but I would retain the ability to log in to my Bitbucket account and hence acces my personal repos using my personal email address. Yes?
No, after the upgrade you will need to log in with your Atlassian account email address; you won't be able to log in with secondary email addresses.
In your case, I recommend either
1) Logging in to each product using separate email addresses, or
2) Creating a work Bitbucket account using your work email and then joining your work team using that account. That way you'll retain access to your personal repositories without having to worry about your work email address.
EDIT: Include two options, clarity
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot