Mapping existing User to a new email address

[Low Herc Zeppelin]

Hi,

I have a use case where existing users will become vendors. They are existing Jira and Confluence users and are AD synced. The issue here is that once they become vendor they will be a new user in the AD and recieve new emails. I want to know if its possible to map they're existing Jira and Confluence user to the new email since they are technically new accounts.

Thanks.

[Peter_DevSamurai]

Hi @Low Herc Zeppelin , 

Unfortunately, in Jira/Confluence cloud, you can’t “map” or merge two separate directory users into one Atlassian account.  If you want to preserve history under one identity, you need to change the email on the existing directory user and let that flow through, rather than creating a brand‑new user.

What you can do right now:

1) Your case: If you must create a brand‑new AD user

• That will normally create a separate Atlassian account when they first access Jira/Confluence.

• Their old issues, comments, page authorship, and group memberships will stay attached to the old account.

• You can:

  • Adjust permissions/groups for the new vendor account.

  • Optionally deactivate the old account once you’re sure it’s no longer needed.

• But you can’t merge the two or transfer authorship/history from old to new.

2) If the same human keeps the same identity in your IdP/AD

• If possible, change their email/UPN on the existing directory user in AD/IdP (not create a new one).

• Let SCIM/SAML sync update the email on the existing Atlassian account.

• So all Jira/Confluence history stays with that same account; only the email/login changes.

I hope the below documents are helpful for you:

- Plan for bulk email address changes

- Email address change via user provisioning problem 

I hope everything works out well for you.

Best regards, 

Peter

[Low Herc Zeppelin]

Hi Peter,

Thanks for the quick response. I see, so it would not be possible to "map" to a new user.

Got it.

Best Regards,

Zeppelin

[Trudy Claspill]

Hello @Low Herc Zeppelin 

There are some things that you could do, if you have appropriate permissions

You could use bulk change operations to reset  some fields, like Reporter and Assignee, to the users' new accounts. Note that will change the Last Updated timestamp for the work items 

You can find a the Filters and Dashboards owned by those users and change the owners to their new accounts.

There are not methods available for changing the identities for activities recorded in the work items history entries nor the author of comments that already exist.

You might be able to automate additional changes such as finding all the items for which a user is a Watcher and adding their new identity as a Watcher. It may require writing custom code that leverages the Jira Rest API