Import epics alongside with its epic work item
What does this MR do and why?
We are working on adding a corresponding epic work item along side every epic. In order to maintain that we need to make sure that every imported epic also creates its correspondent epic work item.
This change is done as a pre-requisite to introducing a NOT NULL constraint to the epics.issue_id column which would help us ensure every epics record would have a corresponding work item record.
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 Alexandru Croitor