Gitea: Close issues as duplicates of other issues

Created on 31 Aug 2017  路  6Comments  路  Source: go-gitea/gitea

Description

There should be a possibility to mark an issue as a duplicate of another issue (autoclosing it). The main issue should have a list of its duplicates, so that one can look through them when needed (an example of this can be seen on Launchpad).

Another option could be to merge issues, but that would IMO overcomplicate things (e.g. order of comments).

kinfeature stale

Most helpful comment

No. That reference just shows up in the comments of the referenced issues. You would have to look through all comments to find the duplicates of the issues you're currently viewing. I mean something like this:

duplicates

The closed issues should show something like "This issue has been closed as a duplicate of #xyz" at the top.

All 6 comments

Do you mean referencing issues like it is in github?

No. That reference just shows up in the comments of the referenced issues. You would have to look through all comments to find the duplicates of the issues you're currently viewing. I mean something like this:

duplicates

The closed issues should show something like "This issue has been closed as a duplicate of #xyz" at the top.

Could be displayed like this. Not sure how the UI for actually marking an issue as a duplicate should look like, though.

duplicates-list
duplicate

Your proposal is absolutely perfect!
I would like to see this solution in Gitea.

Having a section showing a summary of referenced issues seems useful, though the introduction of issue "duplicates" is where engineers start splitting hairs. Once you flag one you need a convenient way to unflagged it is more investigation reveals it's not, in fact, a true duplicate. I believe what's really being sought after here would be better served by label sets for custom taxonomy. YMMV

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

Was this page helpful?
0 / 5 - 0 ratings