Issue Summary

When migrating the projects with the options below, the details of the user who archived the project are not included in the users and groups migration.

Select users and groups
	Only users and groups related to the selected projects
		Include all users and groups assigned to required roles

The entities below are being exported; therefore, the migration status on the dashboard is incomplete however the entire project migration fails.

"archivedBy": "mri:mig:identity:user:jira.userkey/JIRAUSER10200",
"archivedDate": "2024-03-04T15:45:04.703Z",

This is reproducible on Data Center:

Steps to Reproduce

1. Create a project and archive it.
2. Ensure that the user who archived the project is not part of any project role. To achieve this, after archiving the project remove the user from the jira-administrator and jira-software-users group(this step was followed to replicate this issue locally).
3. Create a migration plan and attempt to migrate the archived project.
4. The migration will remain incomplete, and the project error log will display dependency errors for the user who archived it.

Expected Results

The details of the user who archived the project should be included in the user migration, and the project migration should be successful.

Actual Results

The below exception is thrown in the project_key.log file:

2024-03-04 12:51:29.872668631 ERROR TES project-import We couldn't import Project TES because of 1 missing dependencies: User 'JIRAUSER10200'. This caused 4 other items to fail. Check the reasons for the missing dependencies on your server site.

Workaround

1. Add the users to one of the groups that gets migration and then, use the "All users and groups from the Jira directory" migration option. Or,
2. Restore the project, assign a project role to the user who archived the project and ask the user to archive the project again, then retry migrating the project