Maintain related issues after moving issue
Steps to reproduce
- mark issues as related (for example https://gitlab.com/reproduction-group/foss/issues/3 and https://gitlab.com/reproduction-group/just-gitlab/issues/1)
- move one of the issues (for example https://gitlab.com/reproduction-group/foss/issues/3 to https://gitlab.com/reproduction-group/just-gitlab/issues/2)
What is the current bug behavior?
The related issues from the old issue are missing from the new one:
What is the expected correct behavior?
Related issues are copied to new issue.
Possible fixes
Extend ContentRewriter
(app/services/issuable/clone/content_rewriter.rb
) to related issues.
Development log
- Two merge requests were submitted for this issue:
- !15391 (merged): Maintains "Related issues" on the new issue after moving it to another project.
- !16337 (closed): Maintains "Related issues" on the new issue after moving it to another project, and also keeps the "Related issues" on the original issue.
-
UX decided that it was preferable to remove the reference from old issue was it can lead to confusion #13632 (comment 216235212)
- !16337 (closed) was closed in favor of !15391 (merged)
- !15391 (merged) was merged and shipped on %12.3
- Changes were verified against GitLab.com and they are working as expected. See #13632 (comment 221457135) for more details.
Edited by 🤖 GitLab Bot 🤖