Export Github Issues to XLSX or CSV #24634
-
I’ve been trying to export all my Github issues to either Excel or as a CSV file, however, when I try to run the following command from the terminal:
I get prompted to authenticate by entering in my password, but then I get the following returned:
Can anyone assist in helping me understand what I’m doing wrong? Or how else can I export my issues into a CSV / Excel file? Thanks in advance! |
Beta Was this translation helpful? Give feedback.
Replies: 14 comments 6 replies
-
Hi @dfuentes03, Thank you for being here! Unfortunately, we don’t provide the ability to export issues. This is a request that we have received in the past so I will add your request as a +1. I can’t comment on if/when such a feature might be made available, but your request will be seen by the correct team. As an alternative, you can use our API to programmatically export that data: https://developer.github.com/v3/issues/ The data is provided in JSON format. We have some information about creating backups here: |
Beta Was this translation helpful? Give feedback.
-
Thanks for your detailed response, Andrea |
Beta Was this translation helpful? Give feedback.
-
Andrea I too would love the ability to easily export my issues into a spreadsheet to analize the requests from a macro view. Please mark me down as a user requesting this feature. Even if there was a print function to print the list of issues in a printer friendly mode. Currnently I have 5 pages of issues in a project under development and I have to go page by page to print and then the format is pretty ugly-:frowning: |
Beta Was this translation helpful? Give feedback.
-
I have created an OAuth app for my own needs. It currently just exports the title, labels, open date, and modified date. I have opened it up so you can either fork it or make pull requests. Here is the link to the Netlify site: https://github-issues-to-excel.netlify.com/. Here is a link to the source: https://github.com/Joshua-rose/github-issues-to-excel. I hope this helps a little |
Beta Was this translation helpful? Give feedback.
-
Here is a command-line tool (uses the GitHub API referenced) that allows export and import of issues: |
Beta Was this translation helpful? Give feedback.
-
Thanks… I have some private repos, part of an organization that I’m a part of it… but I can’t seem to export those, only my personal repos. any ideas? thanks! |
Beta Was this translation helpful? Give feedback.
-
Wow it’s crazy this functionality still doesn’t exist. As a PM, I would like to be able to download my team’s issues in order to triage the backlog in a more robust project management tool than Github offers (like a spreadsheet!). There are integrations like Unito that will do this but it just seems like such a low-cost high-value thing to build when all that data is already in a table . . . |
Beta Was this translation helpful? Give feedback.
-
You can also check out this one-liner that I created. Worked in my use case: Save GitHub issues as TSV · GitHub |
Beta Was this translation helpful? Give feedback.
-
Hi all! I would be happy if this resource for implementation will help a lot ;D +1 |
Beta Was this translation helpful? Give feedback.
-
It would be a huge help if on the Pull Request filter results page you had an export option. A non-programmer also has needs to pull this information. For our audit compliance we have to provide exports of issues to the auditor, it is very painful to take screenshots of each page of results for each repository. The auditor has also complained they cannot easily make sample selections from screenshots, especially since it's across multiple pages/files. |
Beta Was this translation helpful? Give feedback.
-
I'm surprised this isn't a feature yet. Especially since DevOps and GitHub are both owned by Microsoft now and integrate. DevOps can export a lot easier than GitHub. Seems like it would definitely be worth it and feasible. |
Beta Was this translation helpful? Give feedback.
-
I don’t honestly remember how I got on this thread but I would be happy to
take on the project if GitHub has budget for a PM in this area.
…On Thu, Jul 27, 2023 at 12:11 PM Marie Bakke ***@***.***> wrote:
GitHub needs to increase the urgency of this request. It's mind boggling
that this feature does not exist.
—
Reply to this email directly, view it on GitHub
<#24634 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB5VTIZAZGNGVM7IGV7EJ5TXSK4OPANCNFSM572UMGQA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Is this ticket still open ? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Hi @dfuentes03,
Thank you for being here! Unfortunately, we don’t provide the ability to export issues. This is a request that we have received in the past so I will add your request as a +1. I can’t comment on if/when such a feature might be made available, but your request will be seen by the correct team.
As an alternative, you can use our API to programmatically export that data:
https://developer.github.com/v3/issues/
The data is provided in JSON format.
We have some information about creating backups here:
https://help.github.com/en/articles/backing-up-a-repository