Transferring issues to another repository in an organisation

[kethomassen]

Is there an official way to transfer issues from one repository to another inside a github organisation?

I believe this can be done in a hackish manner using a script, but are you thinking about implementing / already implementing a way to achieve this. This would be really handy!

[holman]

We don't have anything "official", really; probably the best approach would be to use the API and transfer them that way. I'm also willing to bet there's some open source code on github.com already written to do this.

[Scotchester]

In case anyone stumbles across this issue via search, as I did, this script might be useful to you: https://github.com/IQAndreas/github-issues-import

[sjackman]

👍 Transferring issues would be a really useful feature.

[nicolasgarnier]

👍 That would be super useful. Especially for large organisation where multiple projects are interconnected you often have external developers/users miscategorizing issues. A simple way to move an issue between repo or to at least copy an issue (keeping all watchers of the issue) would be great.

[nicolasgarnier]

Alternative would be to have a "triaging" issues queue for Organization where we could then move the issues to a repo in the Org. This would allow Organization members to triage issues after users/dev reports.

[ebidel]

+1 for being able to move issues between orgs.

We run into this issue :P in the Polymer all the time. We have hundreds of repos and users often incorrectly file an issue in the wrong place. Our method to date has been to close the issue and re-open it for the user under the correct repo. Very clunky :(

[cobismith]

+1, it would be great if at least copying, if not transferring, were offically supported.

[mpdehaan]

also also +1, I'm in the process of moving 1 repo into 3 and being able to move everything labelled "foo" would be really nice.

[hostilefork]

+1 ... especially when an issue turns out to be with a subproject or library instead of the repository originally posted against.

[opi]

+1

[rvw]

+1

[jlalvarez18]

+1

[shaunagm]

+1 could definitely use this as well (although I'd utilize a copying functionality more than a transferring functionality)

[arnabk]

+1

[ebidel]

@nicolasgarnier time to share your tool :)

[josemduarte]

👍
The script from @IQAndreas is very good but doesn't preserve the original dates and users. An "official" github issue-copying tool would be really great.

[nicolasgarnier]

Here you go @ebidel :)

I've built an online tool that will help you move issues in the mean time. Try it out:

github-issue-mover.appspot.com

There is some documentation on GitHub but it should be pretty straightforward to use: https://github.com/google/github-issue-mover Although if you are interested to know how to build Dart sever+client app it might be worth a look.

[nicolasgarnier]

I do agree that an official GitHub move issue feature would be way better though :) because when using the API the best we can do is @mention the original user and date but it doesn't quite look like the original issue.

[IQAndreas]

The script from @IQAndreas is very good but doesn't preserve the original dates and users.

I wish it could, but it's just not possible with the GitHub API.

However, the default template (which is also fully customizable) formats the comment in such a way that you can clearly see the date and user of the original issue:

But yeah, the script is a "temporary replacement" for a feature that should be in GitHub to begin with.

[relrod]

+1, please make this a thing. :(

[SV-Li-Bing]

+1

[YannickB]

+1

[tjconnelly]

+1!

[emiltin]

+1

[tylerwhipple]

+1

[jankowtf]

👍

An GitHub-internal option to do this would be super useful!

@nicolasgarnier : awesome little web app! Thx!

[kodawah]

+1

[rebyn]

👍!

[RandomDSdevel]

+1 'cause this would be extremely useful for when somebody files an issue for some fork of another repository and then realizes that it should have been filed upstream.

[RandomDSdevel]

Um…the GitHub Issue Mover doesn't seem to be working right now, so I'm going to try @IQAndreas's script, 'kay?

[nicolasgarnier]

@RandomDSdevel The Issue mover is working fine for me right now. If it's still not working for you feel free to fine an issue here: /google/github-issue-mover/issues

Cheers!

[RandomDSdevel]

@nicolasgarnier: Been there, done that (here's a link if you're interested in how it went down.)

[Merovius]

+1 fwiw. Interested in the "Project with libraries and users don't know where the bug is so assign it wrong"-usecase to, as many here. The issue mover is not a solution, imho, authorship should be retained.

[oz123]

@nicolasgarnier, thanks, your app is great!

[zookoatleastauthoritycom]

+1 I would like github to offer this functionality! I can't use @nicolasgarnier web app because one of the issue collections that I need to move contains confidential information.

[nicolasgarnier]

I promise I won't steal you data @zookoatleastauthoritycom 😆

(More seriously, the project is open source and you could "easily" deploy your own instance... although I realize it's a lot of hassle just to move bugs 😄 )

[rocksfrow]

+1

[inadarei]

+1 please, pretty please?

[holman]

Got it, thanks everyone. 👍

If you want to chat about this further, shoot us an email to support@github.com.