As part of a transition to a single Atlassian Account to access JIRA and Confluence, you'll see a new login experience and will be asked to verify your e-mail starting on Wednesday, April 12th, 2017. Read the entire post for more info.


Delayed Implementation

We're delaying the roll-out of Atlassian Accounts until Wednesday, April 26th, 2017 to address some issues we didn't previously identify.

Over the next few months, Atlassian is moving to a unified account management model for its cloud products; once enabled, you'll be able to use a single Atlassian Account across the Atlassian Cloud ecosystem, which includes instances of JIRA, Confluence, Bitbucket, and HipChat. You can think about this Atlassian Account like you would your Google Account where you use a single Google Account to access GMail, Google Drive, Google Calendar, and other products. Here are the benefits you can expect to enjoy:

  • Short Term - Fewer Passwords: You'll have fewer usernames and passwords to remember for accessing Atlassian products.
  • Long Term - Even Fewer Passwords: If your home institution claims an Atlassian domain, they may enable Single Sign-on using your institutional credentials (e.g., Kerberos ID at MIT for Atlassian Accounts) in the future.

On Wednesday, April 12th, we'll enable the Atlassian Account feature on our Atlassian Cloud instance, which hosts JIRA and Confluence. Once that happens, you'll go through an e-mail verification process where you upgrade your account to an Atlassian Account. The process should be quick and painless and will look like this, but may differ depending on your particular situation:

If you'd like to learn more about how the Atlassian Account works, check out this Atlassian Support article: If you have any questions or comments about this process or how it may affect you, please reach out to the Open Source Team on Slack.