Do not add issue_id to epic resource_label_events when promoting issues
What does this MR do and why?
When promoting an issue to an epic, we copy
resource_label_events to the target epic. In
the process, we need to avoid copying the original
issue_id value from resource_label_events records
so they only belong to the new epic
References
Screenshots or screen recordings
| Before | After |
|---|---|
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #514594 (closed)