Set email aliases

Bitbucket uses email aliases to associate your configured DVCS (Git or Mercurial) with your Bitbucket account. Other users can also find you using any of your email aliases.

Email aliases are different from the email address that you use to log in to Bitbucket Cloud. They are additional email addresses that act as aliases to identify your account.

Primary email alias

You have one primary email alias, which is your Atlassian account email address. An Atlassian account is a single sign-on service that allows you to log in to all your Atlassian Cloud services with one account. Not only do you use this address to log in, but Bitbucket also uses your Atlassian account email address to send you notifications.

To change your Atlassian account email address:

  1. From your avatar in the bottom left, click Bitbucket settings.
  2. From the Account settings page, click Atlassian account.
  3. From your Atlassian account, click Change email address.
  4. Enter your new email address and click Change email.
  5. To complete the process, you need to confirm your new email address. Go to your new account's email and follow the instructions in the confirmation email.

Linked commits

When you add your DVCS email as an alias to your Bitbucket account, you associate your user account with any commits that you push. If the global default for your DVCS is not configured or if you have not validated your email address, Bitbucket does not recognize you as the one who made the commit. As a result, only your configured DVCS username appears.

In the following image for example, the second (top) commit includes a mapped DVCS and Bitbucket account. Alternatively, the user on the initial (bottom) commit is not mapped. As you can see when you hover over the avatar or username, the following words appear: Author not mapped to Bitbucket users.

To map your username to a commit, you need to do the following:

  • Make sure the email address configured on your DVCS matches an email alias on your Bitbucket account. To add an email address to your DVCS, configure Git and Mercurial with a global username/email. You can also configure a repository-specific username/email, but then your Bitbucket account needs to include your global and repository email addresses.
  • Make sure to confirm all your email aliases. If you don't have the confirmation email, you can resend it.
  • Include your DVCS username as a username alias if you have multiple Bitbucket accounts. In the case of multiple accounts, you can mistakenly commit your code under an email address that maps to an account name you did not intend. To map the existing commits on a repository to a different account, go to the Username aliases page under the repository's settings. You must have admin rights on the repository to find this page. For more information, see Set your username for Bitbucket Cloud actions.

Email confirmation

When you add a new email alias to your account, Bitbucket sends you an email containing a confirmation link. Until you confirm that address, Bitbucket can't display your account name with your commits properly and other users can't find you by that email alias. If you haven't confirmed your email address, a banner appears across the top of Bitbucket when you log in.

If you've misplaced your confirmation email or it expired, do the following:

  1. From your avatar in the bottom left, click Bitbucket settings.
  2. Select Email aliases under General.
  3. Click the resend confirmation link next to the address.
  4. Open your confirmation message from your email to confirm.
Last modified on Dec 1, 2017

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.