Migrating Jira Server to Cloud via JCMA with scoped users/groups fails due to membership related errors

Issue Summary

When migrating from Server to Cloud via JCMA and asking JCMA to migrate only the users/groups related to projects getting moved over, migration may fail with a membership related error.

Steps to Reproduce

1. Setup JCMA to migrate a few projects and select the option to use scoped Users/Groups.
2. Attempt to migrate.

Expected Results

Migration goes through.

Actual Results

It fails with the error below:

100:Memberships contain groups that are not part of groups being migrated. 

Workaround

Currently, JCMA has a bug in its Scoped Users/Groups migration that will cause JCMA to fail if any of the groups to be migrated has JSD/JSM only access.

To workaround this, one could leverage the URL below to see which groups will be migrated as part of a project scoped migration:

<BASE-URL>/rest/migration/latest/debug/export/users-groups?projectKeys=<PKEY>&mode=<REFERENCED>

Then with the list of groups, access one by one in Jira and check which ones have JSD/JSM access only. For those, the option is to either remove JSD/JSM access leaving the group without access to any apps or to add a JSW/Core access to the group.

Once that's done, re-try the migration and it should go through.