Copy iteration system notes on moving issue
What does this MR do and why?
Related to #360319 (closed)
When an issue is moved from one project to another, iteration system notes (backed by the model ResourceIterationEvent
) did not get copied over.
This MR contains a fix for the bug.
How to set up and validate locally
-
Pick a group that has at least two projects.
-
Create a new iteration cadence for the group.
How to create a cadence and add an iteration
- Create a new issue and assign the iteration you just created. Then move the issue to another project using the quick action command
/move
.
/move <project fullpath>
Observe that the system note about the iteration assignment is copied to the new issue.
- If you repeat the previous step on
master
branch, you will notice that the system note does not get copied over when an issue is moved.
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 euko