Skip to content

Add reference ids for legacy epic related links and hierarchy

Nicolas Dular requested to merge nd/epic-related-links-reference into master

What does this MR do and why?

Related issue: #497764

To ensure in the future that every epic and their sub-issue has a work_item_parent_link and every related_epic_link has a RelatedWorkItemLink (which is stored in the issue_links table) we add foreign keys to the legacy epic tables.

We also want to ensure that all deletions on the work item side are reflected on the legacy epic side, we add ON DELETE CASCADE to these foreign keys.

Once we backfilled the tables and set the correct foreign key on creation, we can add a NOT NULL constraint to harden the relationship between legacy epics and new epic work items.

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.

Edited by Nicolas Dular

Merge request reports