Move issues from one repository to another on the same organization #1281

New Issue

GiteaMirror · 2025-11-02T03:55:24-06:00

GiteaMirror commented

2025-11-02 03:55:24 -06:00

Originally created by @lunny on GitHub (Nov 27, 2017).

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.

Originally created by @lunny on GitHub (Nov 27, 2017). 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.

GiteaMirror added the type/feature issue/confirmed labels 2025-11-02 03:55:24 -06:00

GiteaMirror closed this issue

2025-11-02 03:55:25 -06:00

GiteaMirror commented

2025-11-02 03:55:26 -06:00

@lofidevops commented on GitHub (Jan 24, 2018):

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).

@lofidevops commented on GitHub (Jan 24, 2018): 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).

GiteaMirror commented

2025-11-02 03:55:26 -06:00

@lunny commented on GitHub (Jan 25, 2018):

Copy-and-close is better.

@lunny commented on GitHub (Jan 25, 2018): Copy-and-close is better.

GiteaMirror commented

2025-11-02 03:55:26 -06:00

@WAMH commented on GitHub (Nov 22, 2018):

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)...

@WAMH commented on GitHub (Nov 22, 2018): 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)...

GiteaMirror commented

2025-11-02 03:55:26 -06:00

@lunny commented on GitHub (Nov 23, 2018):

@WAMH no people are working on this.

@lunny commented on GitHub (Nov 23, 2018): @WAMH no people are working on this.

GiteaMirror commented

2025-11-02 03:55:26 -06:00

@stale[bot] commented on GitHub (Jan 22, 2019):

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.

@stale[bot] commented on GitHub (Jan 22, 2019): 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.

GiteaMirror commented

2025-11-02 03:55:26 -06:00

@techknowlogick commented on GitHub (Jan 22, 2019):

Setting review/confirmed label so stalebot ignores this issue

@techknowlogick commented on GitHub (Jan 22, 2019): Setting review/confirmed label so stalebot ignores this issue

GiteaMirror commented

2025-11-02 03:55:27 -06:00

@6543 commented on GitHub (Jan 28, 2020):

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

@6543 commented on GitHub (Jan 28, 2020): 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

GiteaMirror commented

2025-11-02 03:55:27 -06:00

@lifeofdan commented on GitHub (Feb 26, 2020):

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.

@lifeofdan commented on GitHub (Feb 26, 2020): 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.

GiteaMirror commented

2025-11-02 03:55:27 -06:00

@sigma-frossignol commented on GitHub (Aug 20, 2020):

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

@sigma-frossignol commented on GitHub (Aug 20, 2020): People creating issues in the wrong repo is a recurring issue in my organisation, this feature would be really great.

GiteaMirror commented

2025-11-02 03:55:27 -06:00

@n3storm commented on GitHub (Jun 15, 2021):

We have a triage project where we work on misc issues.
When issue grows to own project, it would be great to be able to move issues.

@n3storm commented on GitHub (Jun 15, 2021): We have a triage project where we work on misc issues. When issue grows to own project, it would be great to be able to move issues.

GiteaMirror commented

2025-11-02 03:55:28 -06:00

@lunny commented on GitHub (Jun 15, 2021):

duplicated as #453

@lunny commented on GitHub (Jun 15, 2021): duplicated as #453

GiteaMirror referenced this issue

2025-11-02 11:56:20 -06:00

[PR #1321] [MERGED] Fix delete user failed on sqlite #15861

GiteaMirror referenced this issue

2025-11-02 12:00:29 -06:00

[PR #1737] [MERGED] fix delete user failed on sqlite (#1321) #16022

Sign in to join this conversation.