- Merge issue
- Close issue
- Copy the description and comment thread of
Ainto an issue thread of
- Copy over description award emoji (maybe).
- https://gitlab.com/gitlab-org/gitlab-ce/issues/31752 closes an issue as a duplicate with a system note.
- gitlab-ee#2303 expands on !10391 (closed) and elevates the linkage to a first class citizen in the connections widget.
If there is an (obvious) issue, it often gets reported multiple times, independently. Sometimes simply closing such reports on the same thing can be simply closed as duplicate.
However, sometimes each of the reports contains information not found in the other issues. So, while they all relate to the same underlying problem, they are not really duplicates. They should all be closed simultaneously (and: none of them should be closed early, as all (may) contain valuable information for the final resolution.
We already have cross references, but I think this doesn't solve the underlying issue, as they are too loosely coupled. Also, anybody and their dog can cross-reference issues, whereas deciding whether two reports refer to the same thing should probably be left to someone in the knowe (e.g. a dev/admin/...)
Provide a mechanism to merge two issues (and probably also to unmerge them).
I see two possibilities:
two issues become one: you get to the very same information regardless of whether you go to
issues/666; probably you are just redirected to the main issue when browsing to the secondary one. All posts that were sent to any of the issues individually are shown. (This is probably not such a splendid thing, since the issues only allow for a linear non-threaded discussion, and merging two discussions could cause great confusion)
the two issues are linked only in their metadata: whenever any one is closed/reopened/assigned/tagged/..., this operation applies to all merged issues. the page for each issue should make it obvious, that it is merged with another issue.
This is btw the way the Debian folks handle it in their battle-tested BTS.