Requeue backfilling epics to work items
What does this MR do and why?
Draft because we want to have all syncing problems fixed before merging this MR: https://gitlab.com/gitlab-org/gitlab/-/issues/463057
Requeue backfilling epics to work items
We requeue the backfill migration because we backfill the data in two steps:
-
The initial backfilling created a work item for every epic to unblock any follow-up migrations that depend on the work item data. At the time we ran the migration, we did not sync epic to work item data by default in the application layer.
-
The second backfilling (this one) re-syncs the data again to make sure it's up to date. At this time we enabled syncing epic to work item data already by default.
Changelog: changed
Issue: #462878 (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
Before running the migration:
Epic.last.title
Epic.last.work_item.title
# Both titles should be the same, now let's modify them to get out of sync
Epic.last.work_item.update!(title: 'another title')
Run the migration bin/rails db:migrate
# Both titles need to be the same again
Epic.last.title
Epic.last.work_item.title