Project lead user disappeared after restore database

[Ragnar]

Hi!

I restored old database into new Jira user account (woodpeckersystems.atlassian.net). All the issues were imported, but It shows that project MAIN Lead user is empty (atlassian.net/secure/BrowseProjects.jspa). I can not change it (Oops, looks like we’re having issues. Try again and we’ll give it another shot"). It seems that the person who created woodpeckersystems Jira are now deleted after restoring database into. Should I contact to Jira support and ask to change it to the person I want?

[Angélica Luz · Accepted solution]

Hello Ragnar,

Welcome to Atlassian Community!

Just for a better understanding of the issue, I would like to make some questions:

Is this issue happening on only one project?

Is there any other administrator facing this issue?

Can you please open the developer tools on your browser while trying to change the project lead to check if it shows any additional error?

If possible, send us a screenshot of the error.

Regards,
Angélica

[Ragnar]

This issue happening on only this project called "MAIN".

There are no other administrators because I was the second one but the first administrator/owner disappeared.

1. When I move mouse cursor to the user it gives this kind of error:

2. Developer tools give me this kind of error after I try to open "User" link:

commons.3f53cbdaf928c775f4a5.8.js:1 Error: Service user not found: Request failed with status code 404
at t (async-people-profiles.2280cfe7e98d300708c3.8.js:1)
at new t (async-people-profiles.2280cfe7e98d300708c3.8.js:1)
at Function.A.from (async-people-profiles.2280cfe7e98d300708c3.8.js:1)
at async-people-profiles.2280cfe7e98d300708c3.8.js:1
at Object.next (async-people-profiles.2280cfe7e98d300708c3.8.js:1)
at g (async-people-profiles.2280cfe7e98d300708c3.8.js:45)
at _ (async-people-profiles.2280cfe7e98d300708c3.8.js:45)
at e.value (async-people-profiles.2280cfe7e98d300708c3.8.js:45)
at Object.onNext [as next] (async-people-profiles.2280cfe7e98d300708c3.8.js:1)
at g (async-people-profiles.2280cfe7e98d300708c3.8.js:45)
at _ (async-people-profiles.2280cfe7e98d300708c3.8.js:45)
at e.value (async-people-profiles.2280cfe7e98d300708c3.8.js:45)
at async-people-profiles.2280cfe7e98d300708c3.8.js:1

[Angélica Luz]

Thank you for the details, Ragnar.

Searching using the details you provided, I was able to find that this issue is related to a bug, but don't worry, there is a fix for that.

• User created with admin username when an instance is subscribed

To fix the issue it's necessary to contact our migration support team, so they can access your site and also confirm the details of the account. Since community is public, we won't post any sensitive information, that's why the ticket is better in this case, so only us from Atlassian and you will have access.

I see that you created a ticket with our support and they updated the project lead through, that actually is not the resolution for the bug, so if you have any other issue related to the other admin that was the project lead, you can check with them to move the ticket to migration or create a ticket directly with the migration team.

If you have any questions, please let us know.