Diagnostics report for Bitbucket Cloud post migration

Problem statement

After a migration (successful or failed) there is no way to check within the CMA if the source and destination site data are equal for the migration plan. Being able to see this data automatically directly after the migration has run will enable early detection of issues and subsequent resolution.

Suggested solution

1. Add post-migration checks as a diagnostic report to the migration dashboard.
2. Examples of datapoints on this report (from source and destination workspace for the migration plan that ran) for Bitbucket
   1. Total number of users
   2. Total number of groups
   3. Total number of repositories
   4. Total number of pull requests

Workaround

To audit pull requests, please see https://bitbucket.miwalker.net/projects/BBCS/repos/audit-pullrequests/browse