Skip the list of users/groups without any global permissions in the pdf report.

[daniel-borek-sonarsource]

A project transfer will produce a pdf report that contains list of users for whom global permissions can't be transferred. The report lists all users, regardless of whether they have any permissions or not.

In a case where we only have a small number of users and groups with any global permissions, but thousands of users overall, the report ends up being overly verbose, listing all usernames rather than only those that we should focus on.

[okorach-sonar]

Posting this as a first analysis. @daniel-borek-sonarsource I can see what workflow could cause the above problems. We'll need more inputs from the end user.

From my tests, in the migration report:

• In the Projects table there seem to be no detail of the list of users whose project permissions are not migrated, only the count of it, this is not causing a huge report, and is the intended behavior

• In the Limitations section, the list of users who had GLOBAL permissions of some sort is liste but this should be a small number of users (that have global permissions), so it is OK to list them all.

[okorach-sonar]

Problem is now understood. The long enumeration of users is in the "Migration Limitations" section, as per the screenshot above.
So, the fix should be that:

• In the "Migration limitations" section the report should only contain the first 10 users explicitly and only a count of the rest. For instance: <n> user(s) had global SonarQube Server permissions and were not migrated to SonarQube Cloud (first 10:<user1>, <user2>, <user3>, <user4>, <user5>, <user6>, <user7>, <user8>, <user9>, <user10>).
• If the list of users is less than 10, the message becomes: 4 user(s) had global SonarQube Server permissions and were not migrated to SonarQube Cloud (<user1>, <user2>, <user3>, <user4>).