I have seen many questions about people asking to merge ID's. But this is a little different, as I am trying to determine if I even should do that.
I suspect my situation will be similar to many:
On bitbucket I have a personal account, my day job account/team, and my side-job account/team, Currently, I just use my personal email address for all, and forward emails to the day-job email, or side-job email according to Gmail filters.
I manage a JIRA instance for my day-job (day-job-email) and side-job (side-job-email).
My side-job also uses Confluence (day-job-email).
By using my personal for BB, it means two sign in's to jump between BB to JIRA or to Confluence. With TFA enabled, this is pretty annoying. There are a few other annoyances with these being seperate.
Everyone seems to want to merge their ID's. I think merging ID's would be a mess for me.
I think the ideal would be the ability for the Atlassian ID to have multiple email addresses associated with it, and for each service-instance, you can choose one of those email addresses to be communicated on.
Putting everything under my personal email is not an option, as my companies require you use company email for JIRA. I think this is common.
Then my option is to keep everything separate. This would mean creating a few more bitbucket accounts... uggh. I imagine that will make SourceTree crater (but what doesn't).
How are others managing this situation? Are their plans to make this better?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs