Gitea: Move issues from one repository to another on the same organization

[lunny]

Sometimes we need split one repository into multiple, but the issues can not be split. If this feature has been implemented, it's very useful. This operation could ask admin permission of organization.

[lofidevops]

At https://github.com/gogits/gogs/issues/4499 there was a suggestion to solve a similar request with a copy-and-close mechanism rather than a literal move. This would preserve issue and link history.

I'd also suggest that copying/moving issues between organizations is useful (not sure how to handle permissions).

[lunny]

Copy-and-close is better.

[WAMH]

Has this been addressed, or is there a workaround? It is a pain to copy an issue and all its comments and uploads. In our case, it is sometimes because of a simple mistake (posting on another repo by mistake, then needing to move the issue to the right repo)...

[lunny]

@WAMH no people are working on this.

[stale[bot]]

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.

[techknowlogick]

Setting review/confirmed label so stalebot ignores this issue

[6543]

Idear: copy issue; close orig; move comments on orig(they are moved); setup a redirect to new location

This schould prevent links from breaking and you have a nice redirect. eafen links to issuecomment schould be aave if we move them rather than copy-them

[lifeofdan]

Yes, I would love this feature as well. In a big project, it is not uncommon for people to create the issue on the wrong repo and then need to move it later. Especially if the people creating the issue are not super familiar with the code base.

[sigma-frossignol]

People creating issues in the wrong repo is a recurring issue in my organisation, this feature would be really great.