Fetch related epic links from work items
What does this MR do and why?
This starts reading related_epic_links from the work item side, instead of the legacy epic side.
The reason why we can start doing this is because we started creating related epic links
through the work item service first. So they become the source of truth.
This is the first step to be able to remove data from
related_epic_links (e.g. target and source) and only keep the id, issue_link_id in the table.
References
Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
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
This visualization might explain it the best:
- We get the data from the work item links and only use the ID from the related_epic_link in the presenter
- In the future we can remove more columns from related_epic_links table and only keep the ID
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.