Investigate setting up tests on staging for migration of epics to work items
Related to gitlab-org&11777 and gitlab-org&12738 (closed)
The Epic Work Items Migration Working Group would like help implementing tests on staging for validating data sync between legacy epics and new work item epics. An e2e test would create an epic and then the data between the legacy epic and work item epic would be compared.
Data that needs validation:
- created_at
- updated_at
- closed_at
- author: id
- iid
- namespace: id
- title
- description
- state
- start_date
- due_date
- start_date_is_fixed
- start_date_fixed
- due_date_is_fixed
- due_date_fixed
- confidential
- labels
- upvotes
- downvotes
- color
- text_color
Update:
A scheduled pipeline is now running every day: https://ops.gitlab.net/gitlab-org/quality/staging/-/pipeline_schedules (Epic migration testing)
- when creating a legacy epic creates a duplicate work item epic
- syncs epics dates when editing a milestone
- when updating an epic
-
- syncs changes from legacy epic to work item epic (update title and description)
-
- syncs changes when adding an issue with milestone
-
- syncs changes when changing confidentiality
Edited by Désirée Chevalier