Add capability to handle labels unified between epic and work item
What does this MR do and why?
Add capability to handle labels unified between epic and work item
While migrating Epic to Work Item for a short period of time we need to be able to handle some associations, in this case labels, linked to both the Epic and its corresponding Work Item.
This would allow us a smooth transition from using the Epic object to using its correspondent Work Item.
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
Examples of queries:
-
Epic.find(941053).labels.where(title: "UX")
, plan: https://console.postgres.ai/gitlab/gitlab-production-main/sessions/28488/commands/88956 -
Epic.find(941053).labels.find_by_id(2024184)
, https://console.postgres.ai/gitlab/gitlab-production-main/sessions/28488/commands/88957
Query Description | Before | After(labels filtering on a UNUION between legacy epics and epic work items) |
---|---|---|
Epic list filtered by: typefeature AND devopsplan OR devopsdata stores OR devopsverify |
https://console.postgres.ai/gitlab/gitlab-production-main/sessions/28693/commands/89441 |
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.