Maintain related issues after moving issue

I would absolutely say yes. Moving an issue is essentially changing the parent relationship. I would almost take it a step further and expect the old issue to disappear entirely as it adds a level of confusion when someone stumbles across an issue that was "moved" but is out of date with the "moved" issue.

Is there a particular reason why we keep the old version around?

Is there a particular reason why we keep the old version around?

@gweaver I'm not sure if this is the reason but it can happen that people who had access to the issue prior to moving have no longer access to it after moving. This could mean people loose access to comments they wrote.

@winh, @gweaver, @annabeldunstone I've built another solution that keeps the related issues in the old one and duplicates them in the new issue https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/16337

So from a UX perspective, we need to decide between:

https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/15391: Maintains "Related issues" on the new issue after moving it to another project.
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/16337: Maintains "Related issues" on the new issue after moving it to another project, and also keeps the "Related issues" on the original issue.

Hopefully we can do that before Plan for moving issues between CE and EE

Screenshots

Output of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/15391

Old issue	New issue

Output of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/16337

Old issue	New issue

@winh I guess this may be more of a philosophical comment, but who or what owns an Issue? From my vantage point, an issue belongs to a project and is owned by that project. Any comments on the issue also "belong" to that project. If an issue moves, the issue belongs to another project. Wouldn't it naturally follow that if this were the case and the moved issue is no longer accessible, comments also being no longer accessible may be the desired case?

I'd love to better understand the historical context around this decision.

I'd love to better understand the historical context around this decision.

It's a good question. I think there has been a lot of confusion over this copy feature:

I think the rationale was discussed in https://gitlab.com/gitlab-org/gitlab-ce/issues/3024#note_3684985.

comments also being no longer accessible may be the desired case?

I see arguments for either way—so I would leave the decision to your or UX.

I just see some potential frustration of users who spent a significant amount of time writing a comment and then are no longer able to access it. Imagine for example if we would make gitlab-ee a private project and community contributors would no longer be able to access their feature proposal after we decided to make it an EE-feature.

@mayra-cabrera thanks for the MRs and the screenshots.

Can you confirm my following assumption on the behavior of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/16337:

If we maintain the related issues on the closed issue and the new issue, a given issue that was marked as related will also conversely have a related issue for both the closed and the new issue.

If my assumption is correct, I do not think we should maintain related issues on the closed (moved) issue because it will create two references to the same root issue on those issues that are related, leading to even more confusion.

If my assumption is correct, I do not think we should maintain related issues on the closed (moved) issue because it will create two references to the same root issue on those issues that are related, leading to even more confusion.

That's right. That's why I opted for moving the references.

Sorry for the delay here @winh and @mayra-cabrera!

I agree woth @gweaver. I think seeing duplicate related issues (one closed and the newly moved one) on an issue is unnecessary and confusing.

I think we should move forward with removing the references to the closed/moved issue.

For reference we've also discussed moved issues here- &633 (comment 191012652)

I would love to hide or delete the original moved/promoted issue. I'm hoping we can conduct some research in the near future to find out if users actually have a need to view the original issue (ux-research#361 (closed))