Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

All migrated Jira users now "Former user", did parallel Confluence migration confuse things?

Steve Loyola
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 20, 2019

I just migrated from server instances of Jira (v8.5.1) & Confluence (v7.0.4) into a single cloud account for both Jira and Confluence. The Confluence migration worked beautifully with all pages showing which users have edited that page, etc.

All the Jira content appears to have migrated fine, but all issues now show "Former user" for Assignee and Reporter, even though those users *appear* to be in the new cloud system.

I can see that the system knows that not all Former users are the same because if I hover over "Former user" and choose "Assigned Issues" for what I know are two different users in the old system, I'm sent to a search forms with different 24-character hex "assignee" ids.

So, I can't help but wonder, did running the Confluence migration first cause the Jira migration to not be able to map the Jira users correctly?

More importantly, how can I fix this?

Thanks!

1 answer

1 accepted

1 vote
Answer accepted
Steve Loyola
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 21, 2019

Answering my own question...I reset everything then migrated Jira *before* migrating Confluence and everything is peachy now. So, at least in my case, order matters!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events