I had that problem for a day or so, with "answers". I finally went to my 'answers' profile, and saved it without making any changes, and my mail started going to the new location.

DID NOT WORK! Changed my email on this page https://id.atlassian.com/manage/account-settings#, but it still shows my old email on this page https://coolmediadev.atlassian.net/wiki/users/viewuserprofile.action?username=<removed> and sends email to my old email - ARGGGHHHHH!

Thanks a lot.

Took you long enough to get it done, should have been available from day one.

Holly.... it actually happened. Did anyone check if pigs started flying in the meantime because I was certain that'd happen sooner
At any rate I am glad I was proven wrong, and I could finally unregister that doomed-to-die e-mail address.

Oh thank my godness.

Goood; thanks !!!

Yay!

Finally! Thank you.

Hi everyone, thanks for your patience.
I'm happy to announce that this feature is finally available to you. You can now update your Atlassian account email address via https://id.atlassian.com/manage/change-email

As apparently Atlassian also can't change the e-mail address of my Atlassian account (I filed a support case to their support to do so), they offered my to move all my support cases, answers, JIRA tickets, comments ... to my new Atlassian ID. I doubt, if this will work.

Companies merge and change their names and emails. This is required.

We have been spending ~ 100k $ for Atlassian products and related add-ons during more than nine years. Apologize - I do not want to be that offensive - but, please understand, that this issue is not acceptable. There must be a way to change the primary e-mail address of an Atlassian customer account. Organizational structures change more than ever expected in such a long time period.

This is pretty silly.

We recently changed our name and may do it again. It is ridiculous that we cannot change users' email addresses - this necessitates me spending license dollars on email accounts that I do not need otherwise.

Well, everything considered, the only possible explanation for the lack of implementation is that there is a low ratio of [corporate interest in this feature vs required implementation effort].
I'm going to assume for the moment that Atlassian is not completely blind and well seeing the need for this feature. This leaves the other part, implementation effort, as the culprit. One thing I can think of is that the code base has-for whatever reason-become unmaintainable. Sadly, I've seen this sort of thing happen. But it also means we are not going to see this 'feature' in the near future. Sorry if I'm stepping on toes here, but the explanations we did get are a bit opaque. Feel free to prove me wrong.

This is absolutely ridiculous. Every other web service (free or paid) has the ability to change an account's email address. My account's email address has been compromised many times according to haveibeenpwned.com. I simply do not want to use it anymore. Apparently this basic feature has been requested for almost 3 years. I'd really like to know the reasoning behind Atlassian's choice of not implementing it.

Yeah, taking a look at your ID-80 and its comments, and the lack of change there, I do not believe you.
Publishing two posts that basically mask what you are or aren't doing behind fancy phrases with no or incorrect meaning is not exactly the kind of reassurance I was looking for.
I still stand by my earlier comment that the implementation of an email-update feature usually takes hours, not years. I can see some change in SourceTree, most of it unnecessary, but none here. I do not understand your priorities.

Hi everyone,
Thanks for your feedback - whilst we did originally begin working on this feature late last year, we pressed pause on some of the work earlier this year but unfortunately, did not update this ticket. Sorry about this. There's a lot of effort and investment going into identity management across Atlassian - this is definitely an area that is currently top of mind. If you'd like to read more details, have a look at the latest update in ID-80.
In the meantime, we have recently recommenced our efforts on this and hope to have this out soon.
Thank you again for all your patience to date,
Cheers,
Helen Hung
Product Manager

Classic Atlassian. Constant stream of new shiny features & products while leaving fundamental issues rotting for years.

Hmm. This is a problem for me. I've since left my employer and need to change my account's email address to my new one. Seems I'm unable? Very disappointing. This is the kind of basic feature I expect from contender software, which when discovered as an oversight leaves me wondering how professional the rest of the software might be. Not so sure I trust Atlassian anymore!

Come on, guys. All customers are desperately waiting for this "feature"!

This ticket is "In Progress" since October 2015... not exactly what one would call progress
Any updates on when this will be fixed?

This is a must-have, please allow it!

+1 for this. A user database that uses email address as the primary identifier and doesn't allow it to be changed? You'd think we were back in the 1990s...

Considering the recent adoption of google logins, and ranking Atlassian login second, I suspect they are considering not maintaining this particular feature at all, and/or hoping people will just stop using Atlassian logins altogether in favor of google accounts. After ... years? I'm still not seeing anyone assigned to this issue.
This isn't exactly the most respectable course of action, and I do frequently bring up this whole mess when Sourcetree is discussed at our university. Sensible developers don't require remote account logins in a free tool just because they can.

Come on!!!!

Any update regarding this issue?
I still can't get over the fact that in 2016 an online tool does not allow you to update your email address. What were they thinking?!

Upvote.

I also vote for this feature.

Guys, it's kinda critical. We've already lost our email for the main account. Is that really so difficult?

Any ETA? We also have to change addresses for some accounts that are expiring.

LOL atlassian

@hhung

Hi Helen,

Can you give us an idea of when this feature is expected to come online? We too have an ID associated with an email address that is about to expire.

Regards,
Maarten

Hi,

Thanks, and I realized I probably should apologize for that earlier comment. There was just too much stacking up. Suddenly I had yet another account on yet another site that was registering me automatically, using an email address that will expire no matter what, and that I could not even fix. Although I am still not sure how significant this account even is, having a readonly email address as sole offsite communication basis is a recipe for communication/account loss. I just can't understand why you are implementing this feature only now, and not right from the start. It seems kind of important...
Anyhow, sorry for my rather aggressive comment from last month.

Hi everyone, thanks for all your comments on this, really appreciate it.
A quick update for you all: we have started working on this. You soon will be able to update your Atlassian account (Atlassian ID) email address - more updates to come as we progress.
Thanks for your continued support!
Helen

I have to say. Suddenly I'm not so unhappy anymore that my account email address is going to expire.
If they can't even implement such a simple feature (this is like what? two hours of work? less?) what else did they not get right? I mean, I never asked for this account either. It just popped up automatically 'oh right, we took your email and made another account for you on this other, totally unrelated, site. You know, just in case'...
SERIOUSLY??????

Ridiculous

Hi guys, I am in the same situation.
I have created a Jira Cloud instance by using my email address in behalf the client. It's time to transfer the ownership of Jira and I've changed the billing contact name but not the email address.
This is unacceptable, the client is annoyed and Atlassian looks unprofessional by not able to update the email address.
I can create an Atlassian Account for the client but I can't link that account to the instance. Why not?

I'm really surprised that the "My Atlassian" ID email address can't be changed after all this time.

Very curious what the barriers are to making this happen... if there's anything the community can do to help, we're here!

Since my company changed domain name, does this mean that we have to transfer the account and have some 3 hundred users to change their atlassian url? This is indeed very cumbersome, when will theis scheme be improved?

Absolutely necessary feature

How can be something as simple as changing an email address is not possible? Seems this should be basic functionality... sad Atlassian admin

What's unacceptable, because of this issue, is that they refused to delete my account after I requested it:

As we cannot automatically delete a created Atlassian ID, what we can do is edit the communication preferences within your Atlassian account so that you will not receive communications from us.

In Canada, we have privacy legislation maintaining users' rights to their personal information. So if we request that an organization remove it, it must comply. So what they're doing here is actually illegal in Canada. I confirmed this by reviewing their privacy policy; they won't necessarily delete all of your data.

I will no longer be opting into any Atlassian products, and won't be recommending them to my clients.

Plenty of alternatives exist, and they're all free and open source (so anyone can contribute fixes or new features - like this issue here), and can be hosted or self-installed:

• Redmine (alternative to Jira)
• GitLab (alternative to Bitbucket)
• Each of the above products includes wikis so Confluence is not necessary.

Any updates on this? This is simply unacceptable.

Agreed – this is a big deal. My corporate email address changed b/c of changes in the company name / domain. The old address will stop working soon, and my best option is creating a new account, entering a support ticket, etc. Yikes.

This is a pretty big deal and should be addressed.

Update on this?

Atlassian, could we please get a status update of this issue? It is completely unbelievable that it was allowed to pass you QA and even more so that you have not started to address the problem yet. Never heard of not being able to update the mail of an account. Please, please fix this.

Why all the verification crap? If you're logged in, you're verified. You should be able to change your own e-mail address just like that.

I wish someone at Atlassian with the authority to move this forward could actually feel my frustration on this issue. An email account is not something that is set in stone. It is fluid and changes. The premise that I cannot update my point of contact data, but can completely move all the associated systems to an entirely different account is like moving the barn because the horse is standing in the wrong spot.
At our company, we have moved the development team to it's own division with appropriate domain and email changes. I NEED to update my email.
1. Store the updated email.
2. Send a change notice to the old email for verification.
3. Verify the change using a link.
4. Verify the new email using a link.
5. Finalize the change.

Although I was able to simply update my HipChat email easily via the online form, so ....

I can change my email and can have 2 emails signed in at all product, but for my atlassian id i cannot have 2 email adresse? Not even can i change that email adress?
ROFL

Well, I thought it is a standard that you can change e-mail whenever you want to. Please tell if there is any reason that it can't be done or shouldn't.

until this change is made i guess the best option is to have the email used for this accessible by different persons in the department in case someone leaves the other can still access it. I know this is not the best secure way or best practices but, it can be a way to prevent total loss.