Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
lunny opened this issue Nov 27, 2017 · 11 comments
Closed

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

lunny opened this issue Nov 27, 2017 · 11 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active.

Comments

@lunny
Copy link
Member

lunny commented 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.

@lunny lunny added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Nov 27, 2017
@lofidevops
Copy link

At gogs/gogs#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 link
Member Author

lunny commented Jan 25, 2018

Copy-and-close is better.

@WAMH
Copy link

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

@lunny
Copy link
Member Author

lunny commented Nov 23, 2018

@WAMH no people are working on this.

@stale
Copy link

stale bot commented 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 stale bot added the issue/stale label Jan 22, 2019
@techknowlogick techknowlogick added issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented and removed issue/stale labels Jan 22, 2019
@techknowlogick
Copy link
Member

Setting review/confirmed label so stalebot ignores this issue

@6543
Copy link
Member

6543 commented 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

@lifeofdan
Copy link

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
Copy link

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

@n3storm
Copy link

n3storm commented 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.

@lunny
Copy link
Member Author

lunny commented Jun 15, 2021

duplicated as #453

@lunny lunny closed this as completed Jun 15, 2021
@go-gitea go-gitea locked and limited conversation to collaborators Oct 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

No branches or pull requests

8 participants