Can't change reporter/assignee after migration from Jira server

Question

Hello all, I thank you in advance just by reading this.

I performed a migration from Jira server to Jira Cloud and used both the backup zip and the data zip.

The projects, issues and what not imported flawlessly but the users of the issues appear in this UUID form.

I have no problem changing the users by hand but every time I try to change a user, I get the error displayed in the second image.

It seems that if I create new issues the problem does not happen. The problem seems to happen only in migrated issues.

Any help would be appreciated, thanks again in advance, and best regards to you all.

simdeasysadmin · Answer

Hello Petter, thank you for the fast response. Please let me answer the questions you asked.

When I said the process worked flawlessly I meant everything except the user mapping part worked flawlessly.

Regarding your first question:
- Since my JIRA server was an old version of JIRA server, my data import was done by uploading the two zip files as stated in the tutorial and I don't recall seeing any errors in the import section but that might have been something I might have missed.

Regarding your second question:
- When I said that "I have no problem changing the users by hand" I meant that since the number of migrated issues was not high, I would be fine reassigning all the issues manually if this error was not occurring and unfortunately no, the assignee/reporter remains unchanged.

Regarding your sentence:
- "I see that the users added to your issues are not currently active and in a weird format. Can you confirm if those users are the ones you imported?"

We had a JIRA and Confluence servers in the organization and the Confluence was recent enough to do the migration via the automatic script and it was via the Confluence import that the users were created. The old Confluence Server was relying the the Jira Server for user management and the Jira Server was relying in a LDAP server for user management.

If I use the new issue view, when I select the new reporter/assignee the user listing dropdown box reappears and if I click away from that box, the issue remains as it was (assigned to the old user)

Please let me know if you need anything else.

Best regards

Petter Gonçalves · Answer

Hello @simdeasysadmin

Welcome to the Atlassian Community!

Please, allow me to go a little bit further in the details provided so we can better troubleshoot the issue and confirm we are on the same page here.

About this sentence:

The projects, issues and what not imported flawlessly but the users of the issues appear in this UUID form.

Since your import did not work flawlessly, can you please confirm what errors/warnings you got from the import client?

About this sentence:

I have no problem changing the users by hand but every time I try to change a user, I get the error displayed in the second image.

Could you please elaborate a little bit more on what do your mean by "I have no problem changing the users by hand"? Are you meaning that the assignee/reporter is changed although the error is returned?

I see that the users added to your issues are not currently active and in a weird format. Can you confirm if those users are the ones you imported?

It's possible that you might be facing the following lack where some users from the External user directory are not imported in Cloud:

It would be great if users managed by an external directory in Jira would be imported during site import

That being said, the behavior above can cause the following bug, where issues assigned to deactivated users can not be edited:

Unable to edit an issue when the user is deactivated

Can you please confirm if the same problem happens when using the inline editing using the new issue view? Check this documentation to know how you can turn on the new issue view.

Let us know if you have any questions.