Create RelatedEpicLink table and model
What does this MR do and why?
Related to #352437 (closed)
In order to support the related epics functionality, we need a new table to store the records.
This table should match the functionality of issue_links
because eventually they will be migrated into one table.
Migration
db:migrate
== 20220211125954 CreateRelatedEpicLinks: reverting ===============================
-- drop_table(::related_epic_links)
-> 0.0057s
== 20220211125954 CreateRelatedEpicLinks: reverted (0.0058s) ======================
db:rollback
== 20220211125954 CreateRelatedEpicLinks: migrating ===============================
-- create_table(::related_epic_links, {})
-> 0.0150s
== 20220211125954 CreateRelatedEpicLinks: migrated (0.0151s) ======================
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Eugenia Grieff