Backfill work items for epics
What does this MR do and why?
This MR iterates over Epic records in epics
table where issue_id IS NULL
and creates a corresponding record in the issues
table. The backfilling also copies the basic fields from epic
table into the issues
table fields.
Note: This MR specifically backfills epics for a single hand selected group. In this instance the selected group is gitlab-org/plan-stage
We do this in order to monitor that the backfilled epics stay in sync and fix any issues on synching, before we run a complete backfilling of all epics and also release this to self-managed customers. This should prevent having to run the backfilling on all epics multiple times.
re &12740 (closed) #441622 (closed)
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.