Just today I've received two invitations for shared repositories that I'll be working with. It doesn't appear there's any way to view/accept these from within my existing BitBucket account?
When trying to click link in email to accept invitation, there's a bunch of auth redirects and I'm left at a page to pick a username - but I don't want one.. I have an existing account.
I've tried clicking on accept link while being already signed into bitbucket and also while not. When not already signed in, I can sign in to my account and am still directed back to a page asking me to pick a username.
I've confirmed that the email address used to send invite is the primary email address of my account. I do have one alias registered, but it's not in play during this transaction.
Any insight into how I can gain access to this repository?
Hi Matt! For what you described, it seems like the email where you're receiving the invitation is not associated to any Bitbucket account, that's why when you click on it you're directed to pick a username (Bitbucket is prompting you to create a new account).
I've searched your email address in our system (the same email address you have associated to this Atlassian account) and I couldn't find any Bitbucket account for it. If you already have a Bitbucket account, please check which email address are you using so they can share the repo with the correct one.
Hope this helps!
Hi Ana, thanks for taking time to look into this. I have verified the email address the invitation was sent to is the same email address as is listed here under my Account Settings: https://id.atlassian.com/profile/profile.action
The odd thing though, I don't login to bitbucket with this email address. But the email I'm actually logging in with is listed nowhere under my account settings.
I don't feel this has ever been right since the merge of bitbucket/atlassian authentication. My username is 'mattklinker' if that helps dig further - I don't want to post email :)
Hi Matt :) Okay, so your username ' mattklinker' has two email addresses associated to it, but none of them is the email address you're using for this Atlassian account.
Bitbucket users can send invitations to any email address whether the recipients are already Bitbucket users or not. If an account already exists, they'll just be added to the repo; if there's no account linked to the email address the invite was sent to, our system will prompt them to create a new account. It is not possible to "redirect" an invitation from one email address to the other.
At this point there are two things you can do:
Let us know if you have any question!
Thanks for the clarification, I was able to resolve by having the invitation re-sent to my bitbucket username rather than any email address.
I don't understand why you can't put this together. If I'm able to login to bitbucket using that atlassian id, then I feel I should be able to receive invitations to that email. It's a strange disconnect that I have to provide a different bitbucket email.
Anyway, my immediate problem is resolved - thank you for clarification.
Hi Matt, I'm glad the problem is resolved!
However, I'm still intrigued by the fact that you said that you're able to log in to Bitbucket using this Atlassian account (as I haven't been able to find any Bitbucket account associated to it).
If you can confirm this and would like to look further into this, let us know and we'll create a Support ticket for you (as we'll need to check different email addresses, etc and we don't want you to display that info publicly :) )
Have a good day!
As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...
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