Create diff report per group
Overview
In the event we have a larger migration wave (>500 projects), we should break apart the diff report per group where the projects are migrated. This may require breaking apart the various diffs generated into a more complex dictionary so we can create a diff report per group.
Tasks
-
Update docs if needed (workflow, runbooks, README, migration metrics, etc.)
Acceptance Criteria
-
Existing UTs pass locally -
100% code coverage on new code
Weight estimation
@leopardm @pprokic @mlindsay @nicki_peric @bryan-may @jordan_ng
Please leave your weight estimation as a reaction to this issue (reference). The final weight will be one level higher than the majority weight.
Move issue to customer facing project
In case of customer facing projects that cannot use the same issue/MR from Congregate
- Once the issue is weighted move it to the customer facing project by changing its epic
- Update milestone and iteration if needed
- Reopen the issue in Congregate
- Make sure the 2 issues are related
- MR's should only exist in Congregate and
- Once you create one from the issue manually update the MR description
- Add the customer facing project issue link to
Closes #<congregate_issue_no> <customer_issue_link>
so that the MR closes both when merged
- Make sure to
/spend
all your time in the customer facing project issue