Import project lost assignment

[tnoiret]

Hi,

We have a local sonarqube comunity edition (9.2.2), contains project with issues and assigments, users manualy created.

We want to migrate to sonarqube enterprise edition (9.2.2), with export / import project and users created with SAML connection.

It’s work, but … we lost Assignment on all issues (users logged in before import).

How to keep assignment during project import ?

On the issues.pb zip exported, we have only uuid for assignment but uuid cannot be the same on the new server

Thank you

[ganncamp (G Ann Campbell)]

Hi,

Your version is past EOL. You should upgrade to either the latest version or the current LTS at your earliest convenience. Your upgrade path is:

9.2.2 → 9.9.2 → 10.2.1 (last step optional)

You may find these resources helpful:

• Upgrade Guide
• LTS to LTS release upgrade notes for 8.9 to 9.9

If you have questions about upgrading, feel free to open a new thread for that here.

If your error persists after upgrade, please come back to us.

 
Ann

[tnoiret]

oops sorry, I made a typo, I am of course the latest LTS version 9.9.2

[ganncamp (G Ann Campbell)]

Hi,

I suspected a typo, but it was in there twice.

@tnoiret

we lost Assignment on all issues (users logged in before import).

How to keep assignment during project import ?

It’s not quite clear to me what happened. You migrated an existing instance and the issues were unassigned?

Or you migrated an instance and after importing projects, (from… where?) the issues in the imported projects weren’t assigned?

Or… something else?

 
Ann

[tnoiret]

I have multiple self hosted Community instance with multiples project inside.

I have create a new Enterprise instance from scratch, i have create users with same login & email & SMC account like actual users on Community instance, and i want to export my community project, import into my enterprise instance and keep assignment.

Thank you

[ganncamp (G Ann Campbell)]

Hi,

Thanks for the detail.

To be really explicit: you’ve got the “same” users in both places, but when you imported a test project from your CE instance, the issues weren’t re-assigned to those users?

 
Thx,
Ann

[tnoiret]

Hi, Yes exatly

[ganncamp (G Ann Campbell)]

Hi,

Thanks for the confirmation. I have speculations about what’s going on here, but they’re only that. I’m going to flag this for the team.

 
Ann

[tnoiret]

Hi

Thank you, i think it’s because uuid is different between the two instances.

Can you give me the proto format for issues.pb, with this i can update manualy users assignement and import into my new instance

Thomas

[alain.kermis]

Hi there @tnoiret,

Thank you for your detailed post.

If I understood correctly, you are trying to migrate data from one DB to another. If this is the case, have you tried setting the user UUIDs in the new instance database to match those in the old instance? That way the issue assignments will still be matched to their respective users.

Regards
Alain

[tnoiret]

Hi thanks for your help but is not working

After update uuid and import original project exports, assign still empty. And i check some issue on database, the field IS empty.

I have a vert short timing so i just use API to update assign after import.

Other bug during import, some issue comment are imported multiple time, i have toi delete this with API too.

[alain.kermis]

Good afternoon again, @tnoiret,

We have delved more into your problem, and we have found a potential solution:

1. Assuming you want to gather all issues, users, etc from the multiple community instances, run the endpoint for EVERY user as follows:

http://<your_server_url>/api/issues/search?assignees=<login_value_of_user_goes_here>

2. Assuming all users are already imported in your new instance, then, for every issue, you can use the key field from the payload(s) you get above, and in your new enterprise instance, use the following endpoint (POST) to assign the user to the same issue (please note: issue key remains the same in new instance when imported, so you will be able to match them like so):

POST api/issues/assign, using params: assignee (login you used in step 1), and issue (key you get in this step)

We found that this field (assignee) is set to NULL on purpose, and there was a ticket for this, and since it did not get much traction, it was closed.

Nevertheless, thank you for your report, and we will look more into it.

Regards
Alain