Add legacy epic related link adapter
What does this MR do and why?
Issue: #500279 (closed)
We want to start writing to the work item first, and then sync to the legacy epic. We do this by wrapping the legacy epics services and transform the parameters to be compatible with the work item services.
To make sure we don't break anything, we now introduced the work_item_epics_ssot
feature flag and either call
the legacy service or the work item service.
Since both services still sync with each other, everything should work, regardless of the state of the feature flag. However, we want to get rid of the legacy services completely and only use the wrapper services in the future. This means that we will create a record from the WorkItem services directly.
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.