Features: Issue export and moving issues between repos #72

roham · Apr 19, 2014

Is there demand for either an Issue export feature or a full-fledged Issue migrator as a feature in ZenHub?

The implementation we are thinking for the Issue migrator is a sort of 'teleport' button and drop-down repo selector to issues which would basically close the active issue and reopen an identical one in the new repo selected.

We could then either embed the comments in the new issue body, create comments from the migrator's account with the original author embedded in the body of each comment, or -- for ZenHub users -- auto-post the comments on their behalf via the GitHub API.

Thoughts?

cc @dete

We've implemented Issue Export, will punt Issue "teleport" for now

roham · Jul 22, 2014

We've implemented Issue Export, will punt Issue "teleport" for now

Export is good, but there doesn't seem to be a means by which to import them again? Would make this feature much more useful. Not opening an issue in case I've missed something.

TobyAbel · May 11, 2015

Export is good, but there doesn't seem to be a means by which to import them again? Would make this feature much more useful. Not opening an issue in case I've missed something.

👍

abrkn · Jul 23, 2015

👍

This function would be highly useful. Right now sitting with a bothersome scenario where we have to move issues from one repo to another. Simply dropping the json export file to the first comment on a new issue would be sweet as apple pie. Would also like the exported file to have more intuitive name than "download".

zachumo · Oct 1, 2015

This function would be highly useful. Right now sitting with a bothersome scenario where we have to move issues from one repo to another. Simply dropping the json export file to the first comment on a new issue would be sweet as apple pie. Would also like the exported file to have more intuitive name than "download".

will punt Issue "teleport" for now

So, is this tracked somewhere?

Naatan · Oct 20, 2015

will punt Issue "teleport" for now

So, is this tracked somewhere?

Lets reopen this one to track.

Right now, issue export is very rarely used - making it hard to justify building the 'import' side of this.

But I do often find myself needing it!

Will keep tracking interest in this request vs others in this repo - so please +1 the OP

azenMatt · Nov 5, 2015

Lets reopen this one to track.

Right now, issue export is very rarely used - making it hard to justify building the 'import' side of this.

But I do often find myself needing it!

Will keep tracking interest in this request vs others in this repo - so please +1 the OP

+1

rgwozdz · Dec 4, 2015

+1

lhavel · Dec 8, 2015

+1

Right now, issue export is very rarely used - making it hard to justify building the 'import' side of this.

derp. Are you kidding? What's the point is "exporting" if there is no import? It's useless without import so it's rarely used.

Maxhodges · Dec 13, 2015

Right now, issue export is very rarely used - making it hard to justify building the 'import' side of this.

derp. Are you kidding? What's the point is "exporting" if there is no import? It's useless without import so it's rarely used.

+1

kevinSuttle · Dec 14, 2015

+1

juanlu91 · Jan 15, 2016

+1

A question on this,

What would you want to do with the issue being moved in it's original location?

Automatically close it? or leave it open?

azenMatt · Jan 15, 2016

A question on this,

What would you want to do with the issue being moved in it's original location?

Automatically close it? or leave it open?

I would say close upon successful move.

kevinSuttle/github#37

kevinSuttle · Jan 15, 2016

I would say close upon successful move.

kevinSuttle/github#37

Agreed, that is what I was thinking as well.

Throwing together some quick wireframes here - this could work like:

'Move issue' button above the 'Export Issue' button

When clicked, this will give you a list of repos in that org that you have push access to - similar to the repo merge tool:

When selected, display a confirmation:

This issue will be closed and moved to [repo name]. Are you sure?

Cancel Move issue

When move issue is selected, two things should happen:

A new issue is opened - by the user who selected 'move issue' in the selected repo. This issue:

Has the same title
An opening comment linking towards the original issue
A single comment containing the following for each comment in the original thread
- Posted by: [user name] On [time]
- Content: [content]
for V1, none of the meta data on labels, estimates, milestone etc will be moved over (we can look into that later based on use and feedback)

The existing issue is closed with the comment:

`Issue moved to [GH link]

The page redirects to the new issue.

Obviously a lot we can do to improve that for future releases, but I think that should at least solve the main pain point here - and be pretty fast for us to implement. Anything I am missing that is a 'must have' for this to be useable?

azenMatt · Jan 15, 2016

Agreed, that is what I was thinking as well.

Throwing together some quick wireframes here - this could work like:

'Move issue' button above the 'Export Issue' button

When clicked, this will give you a list of repos in that org that you have push access to - similar to the repo merge tool:

When selected, display a confirmation:

This issue will be closed and moved to [repo name]. Are you sure?

Cancel Move issue

When move issue is selected, two things should happen:

A new issue is opened - by the user who selected 'move issue' in the selected repo. This issue:

Has the same title
An opening comment linking towards the original issue
A single comment containing the following for each comment in the original thread
- Posted by: [user name] On [time]
- Content: [content]
for V1, none of the meta data on labels, estimates, milestone etc will be moved over (we can look into that later based on use and feedback)

The existing issue is closed with the comment:

`Issue moved to [GH link]

The page redirects to the new issue.

Obviously a lot we can do to improve that for future releases, but I think that should at least solve the main pain point here - and be pretty fast for us to implement. Anything I am missing that is a 'must have' for this to be useable?

That looks awesome.

kevinSuttle · Jan 16, 2016

That looks awesome.

I also think that there is value in exporting everything from one repo (say on GitHub.com) and into another (e.g. GitHub Enterprise).

However, there is a lot more to it than you'd think.
https://help.github.com/enterprise/2.4/admin/guides/migrations/exporting-the-github-enterprise-source-repositories/

kevinSuttle · Jan 19, 2016

I also think that there is value in exporting everything from one repo (say on GitHub.com) and into another (e.g. GitHub Enterprise).

However, there is a lot more to it than you'd think.
https://help.github.com/enterprise/2.4/admin/guides/migrations/exporting-the-github-enterprise-source-repositories/

I think that might be better as an API feature 😉

azenMatt · Jan 19, 2016

I think that might be better as an API feature 😉

It sort of is already, but it's a huge hassle.

kevinSuttle · Jan 20, 2016

It sort of is already, but it's a huge hassle.

Bulk move from the Issues list would be grand.

jeoffw · Jan 21, 2016

Bulk move from the Issues list would be grand.

would be grand indeed +1

katlongo · Feb 4, 2016

would be grand indeed +1

This just went live in v2.15.47

This will give you access to a 'move' button on each issue here -

it is just a v1 of this functionality which allows moving within orgs only, so please let me know any feedback on how well it works!

Also - we will likely follow this up by removing the export button - so please also let me know if you still use the export functionality and why if you'd rather we kept it! 😄

azenMatt · Feb 17, 2016

This just went live in v2.15.47

This will give you access to a 'move' button on each issue here -

it is just a v1 of this functionality which allows moving within orgs only, so please let me know any feedback on how well it works!

Also - we will likely follow this up by removing the export button - so please also let me know if you still use the export functionality and why if you'd rather we kept it! 😄

NICE!

kevinSuttle · Feb 18, 2016

NICE!

Very cool feature, thank you :-)

Maybe "Export" would be handy if you could aim it at something like an internal JIRA instance (workplaces not entirely 100% on GitHub yet) but that is probably too much work.

Cervator · Feb 18, 2016

Very cool feature, thank you :-)

Maybe "Export" would be handy if you could aim it at something like an internal JIRA instance (workplaces not entirely 100% on GitHub yet) but that is probably too much work.

Wishlist for v2:

Bulk moving a whole set of issues.
Maintaining references between issues.
Allow moving from a user to an organization, from an organization to another organization, from an organization to a user

ljm22 · Mar 11, 2016

Wishlist for v2:

Bulk moving a whole set of issues.
Maintaining references between issues.
Allow moving from a user to an organization, from an organization to another organization, from an organization to a user

Is there a timeline for bringing this feature to Zenhub Enterprise?

hellobrian · Mar 15, 2016

Is there a timeline for bringing this feature to Zenhub Enterprise?

Hi @hellobrian - this will be in our next Enterprise release, scheduled for mid-April

azenMatt · Mar 15, 2016

Hi @hellobrian - this will be in our next Enterprise release, scheduled for mid-April

Love this feature.

Any reason why the default behavior is to close the issue though? Could we get a select lane option instead? Or at least a toggle to close on migrate check box?

I haven't wanted to close any of the issues I migrated yet.

chrbradley · Apr 13, 2016

Love this feature.

Any reason why the default behavior is to close the issue though? Could we get a select lane option instead? Or at least a toggle to close on migrate check box?

I haven't wanted to close any of the issues I migrated yet.

Or at least a toggle to close on migrate check box?

Yes - we are going to add this in 👍

azenMatt · Apr 13, 2016

Or at least a toggle to close on migrate check box?

Yes - we are going to add this in 👍

Did 'bulk move' make it into the April release?

kevinSuttle · Jun 16, 2016

Did 'bulk move' make it into the April release?

Did 'bulk move' make it into the April release?

Hi @kevinSuttle - we haven't had a chance to work on this yet. To be fully transparent - the whole team have been heads down on a front end refactor to vastly improve performance. We are going to be able to get back to shipping updates once this is live - targeted for the end of June.

Any reason why the default behavior is to close the issue though? Could we get a select lane option instead? Or at least a toggle to close on migrate check box?

We did manage to sneak this one in recently - so you can now decide if you would like the issue to remain open.

This part will be in our next enterprise release which we will start packing up once the refactor is live.

azenMatt · Jun 18, 2016

Did 'bulk move' make it into the April release?

Hi @kevinSuttle - we haven't had a chance to work on this yet. To be fully transparent - the whole team have been heads down on a front end refactor to vastly improve performance. We are going to be able to get back to shipping updates once this is live - targeted for the end of June.

Any reason why the default behavior is to close the issue though? Could we get a select lane option instead? Or at least a toggle to close on migrate check box?

We did manage to sneak this one in recently - so you can now decide if you would like the issue to remain open.

This part will be in our next enterprise release which we will start packing up once the refactor is live.

@ljm22 - did your v2 whishlist get incorporated in a different Issue? I'm looking to move Issues between organisations, but not sure at this point if Zenhub is considering implementing it or not. Thanks

orbanbalage · Sep 26, 2016

@ljm22 - did your v2 whishlist get incorporated in a different Issue? I'm looking to move Issues between organisations, but not sure at this point if Zenhub is considering implementing it or not. Thanks

did your v2 whishlist get incorporated in a different Issue? I'm looking to move Issues between organisations, but not sure at this point if Zenhub is considering implementing it or not. Thanks

it hasn't yet - this is something we still want to improve - but right now we have a number of higher priority issues that we want to tackle first.

azenMatt · Oct 5, 2016

did your v2 whishlist get incorporated in a different Issue? I'm looking to move Issues between organisations, but not sure at this point if Zenhub is considering implementing it or not. Thanks

it hasn't yet - this is something we still want to improve - but right now we have a number of higher priority issues that we want to tackle first.

@azenMatt Is there a way to move more than one issue at a time?

gsantopaolo · Nov 2, 2016

@azenMatt Is there a way to move more than one issue at a time?

Hi @gsantopaolo - it is currently single issue

azenMatt · Nov 2, 2016

Hi @gsantopaolo - it is currently single issue

Would love ability to do a mass export of all issues in a Repo to CSV or other file format. Had a recent ask to do so and can not find a way to do an export of all issues.

samclachlan · Jan 12, 2017

Would love ability to do a mass export of all issues in a Repo to CSV or other file format. Had a recent ask to do so and can not find a way to do an export of all issues.

Hi @samclachlan - we have an issue for this here - #679

No time frame on this right now, but it is something that we want to offer as part of our reporting suite

azenMatt · Jan 12, 2017

Hi @samclachlan - we have an issue for this here - #679

No time frame on this right now, but it is something that we want to offer as part of our reporting suite

Was hoping there was a way to git clone or branch the repo that contains all the Issue/Epic information still displayed in zenhub. I suspect a mass export is what I am looking for. Is this correct?

isugif · Mar 8, 2017

Was hoping there was a way to git clone or branch the repo that contains all the Issue/Epic information still displayed in zenhub. I suspect a mass export is what I am looking for. Is this correct?

In this way I could create a template of Epics with issues and milestones etc and then clone that repo with all the info and then start filling in the information.

For example, the steps in writing a paper are pretty much identical
Epic - write materials and methods
issue
issue
issue
Epic - write results
Epic - write introduction
etc
etc

isugif · Mar 8, 2017

In this way I could create a template of Epics with issues and milestones etc and then clone that repo with all the info and then start filling in the information.

For example, the steps in writing a paper are pretty much identical
Epic - write materials and methods
issue
issue
issue
Epic - write results
Epic - write introduction
etc
etc

Another vote for being able to move issues between organisations (or in my case, from a user's private fork back to the organisation that the repo was forked from).

ajdlinux · Apr 21, 2017

Another vote for being able to move issues between organisations (or in my case, from a user's private fork back to the organisation that the repo was forked from).

I just used this feature--big help! I would love to see the feature include option to copy assignees (and other GitHub/ZenHub attributes like estimate, label, etc). Maybe a check list of what to include in when copying?

trevars · Apr 24, 2017

I just used this feature--big help! I would love to see the feature include option to copy assignees (and other GitHub/ZenHub attributes like estimate, label, etc). Maybe a check list of what to include in when copying?

Looks like this works within an organization. Is there a way to move issues from one organization to another?

Petermarcu · Oct 6, 2017

Looks like this works within an organization. Is there a way to move issues from one organization to another?

This looks promising for our use case. We have GHE ... I will do more digging, but can anyone here share if you know whether moving issues from one repo to another w/i an org works in GH Enterprise?

richnsoos · Nov 13, 2017

This looks promising for our use case. We have GHE ... I will do more digging, but can anyone here share if you know whether moving issues from one repo to another w/i an org works in GH Enterprise?

Hey @richnsoos it should definitely work! You should see the Move Issue button on the sidebar in the extension on the Board Modal/GitHub Issue page 🎉 - let us know if you don't see it!

kendramoroz · Nov 14, 2017

Hey @richnsoos it should definitely work! You should see the Move Issue button on the sidebar in the extension on the Board Modal/GitHub Issue page 🎉 - let us know if you don't see it!

Hi @kendramoroz can you confirm whether there is any way to move issues across organizations? I work on a very large product that aggregates from many open source organizations on Github and we're currently left copying and pasting issues around. Many times the issue will come into a central repo but the fix needs to go into a different organizations code.

Petermarcu · Nov 15, 2017

Hi @kendramoroz can you confirm whether there is any way to move issues across organizations? I work on a very large product that aggregates from many open source organizations on Github and we're currently left copying and pasting issues around. Many times the issue will come into a central repo but the fix needs to go into a different organizations code.

can you confirm whether there is any way to move issues across organizations

Not currently across organizations - the repositories have to be within the same organization to be transferred.

kendramoroz · Nov 15, 2017

can you confirm whether there is any way to move issues across organizations

Not currently across organizations - the repositories have to be within the same organization to be transferred.

hi @kendramoroz , we do not see it. which version of GHE has the Move Issues button? Thank you!

cc: @rdifrango

richnsoos · Nov 21, 2017

hi @kendramoroz , we do not see it. which version of GHE has the Move Issues button? Thank you!

cc: @rdifrango

@richnsoos Hey Susan! It was implemented quite sometime ago - can you send us a note through support@zenhub.com using your work email to confirm the team you're on using ZenHub Enterprise and we can check to ensure you're on the latest version for your team?

kendramoroz · Nov 22, 2017

@richnsoos Hey Susan! It was implemented quite sometime ago - can you send us a note through support@zenhub.com using your work email to confirm the team you're on using ZenHub Enterprise and we can check to ensure you're on the latest version for your team?

My mistake, I thought this was an add on Service for GitHub Enterprise but it sounds like ZenHub is entirely separate. Thanks for quick response.

richnsoos · Nov 22, 2017

My mistake, I thought this was an add on Service for GitHub Enterprise but it sounds like ZenHub is entirely separate. Thanks for quick response.

roham added question labels Apr 19, 2014

roham closed this Jul 22, 2014

azenMatt reopened this Nov 5, 2015

azenMatt added needsVotes and removed Question labels Nov 5, 2015

azenMatt closed this Feb 17, 2016

drdanz referenced this issue Feb 29, 2016
Closed
Moving issues among repositories #84

ZenHubIO/support

Join GitHub today

Features: Issue export and moving issues between repos #72

Comments

roham commented Apr 19, 2014

roham added question labels Apr 19, 2014

This comment has been minimized.

roham commented Jul 22, 2014

roham closed this Jul 22, 2014

This comment has been minimized.

TobyAbel commented May 11, 2015

This comment has been minimized.

abrkn commented Jul 23, 2015

This comment has been minimized.

zachumo commented Oct 1, 2015

This comment has been minimized.

Naatan commented Oct 20, 2015

This comment has been minimized.

azenMatt commented Nov 5, 2015

azenMatt reopened this Nov 5, 2015

azenMatt added needsVotes and removed Question labels Nov 5, 2015

This comment has been minimized.

rgwozdz commented Dec 4, 2015

This comment has been minimized.

lhavel commented Dec 8, 2015

This comment has been minimized.

Maxhodges commented Dec 13, 2015

This comment has been minimized.

kevinSuttle commented Dec 14, 2015

This comment has been minimized.

juanlu91 commented Jan 15, 2016

This comment has been minimized.

azenMatt commented Jan 15, 2016

This comment has been minimized.

kevinSuttle commented Jan 15, 2016

This comment has been minimized.

azenMatt commented Jan 15, 2016

This comment has been minimized.

kevinSuttle commented Jan 16, 2016

This comment has been minimized.

kevinSuttle commented Jan 19, 2016

This comment has been minimized.

azenMatt commented Jan 19, 2016

This comment has been minimized.

kevinSuttle commented Jan 20, 2016

This comment has been minimized.

jeoffw commented Jan 21, 2016

This comment has been minimized.

katlongo commented Feb 4, 2016

This comment has been minimized.

azenMatt commented Feb 17, 2016

azenMatt closed this Feb 17, 2016

This comment has been minimized.

kevinSuttle commented Feb 18, 2016

This comment has been minimized.

Cervator commented Feb 18, 2016

drdanz referenced this issue Feb 29, 2016

This comment has been minimized.

ljm22 commented Mar 11, 2016

This comment has been minimized.

hellobrian commented Mar 15, 2016

This comment has been minimized.

azenMatt commented Mar 15, 2016

This comment has been minimized.

chrbradley commented Apr 13, 2016

This comment has been minimized.

azenMatt commented Apr 13, 2016

This comment has been minimized.

kevinSuttle commented Jun 16, 2016

This comment has been minimized.

azenMatt commented Jun 18, 2016

This comment has been minimized.

orbanbalage commented Sep 26, 2016

This comment has been minimized.

azenMatt commented Oct 5, 2016

This comment has been minimized.

gsantopaolo commented Nov 2, 2016 • edited Edited 1 time gsantopaolo edited Nov 2, 2016 (most recent)

This comment has been minimized.

azenMatt commented Nov 2, 2016

This comment has been minimized.

gsantopaolo commented Nov 2, 2016 •

edited

Edited 1 time

gsantopaolo edited Nov 2, 2016 (most recent)

trevars commented Apr 24, 2017 •

edited

Edited 1 time

trevars edited Apr 24, 2017 (most recent)