# Hack: Easiest way to export issues to CSV

**URL:** <https://forum.gitea.com/t/hack-easiest-way-to-export-issues-to-csv/8038>\
**Category:** Install/Maintain/Configure\
**Created:** [November 1, 2023, 5:06am UTC](https://forum.gitea.com/t/hack-easiest-way-to-export-issues-to-csv/8038 "2023-11-01T05:06:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![benjifranklink](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/benjifranklink/32/4145_2.png) [@benjifranklink](https://forum.gitea.com/u/benjifranklink)\
**Post date:** [November 1, 2023, 5:06am UTC](https://forum.gitea.com/t/hack-easiest-way-to-export-issues-to-csv/8038/1 "2023-11-01T05:06:00Z")

</div>

I need a quick way to export issues to CSV. Gitlab makes it super easy with one-click but apparently not Gitea, yet.

I found this forum and downloaded some code and started futzing with it. Then I realized, “wait, maybe I should just use Gitlab’s importer to import the whole project to GItlab and then I can export the issues from there!” I can still use Gitea and just delete the repo from Gitlab after importing but I’ll have the CSV export.

And this is what I did. It works.

That said, Gitea should have an easier built in data export for issues.

Gitlab import interface happens when you start a new project:

 ![Imprt project](https://us1.discourse-cdn.com/flex020/uploads/gitea/original/2X/3/343f365852be5ee9fc6a3ed8cf0ca6a7bcc1d90c.png)

---

<div class="post-metadata">

**Author:** ![lunny](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.gitea.com/lunny/32/4701_2.png) [@lunny](https://forum.gitea.com/u/lunny)\
**Post date:** [November 1, 2023, 8:28am UTC](https://forum.gitea.com/t/hack-easiest-way-to-export-issues-to-csv/8038/2 "2023-11-01T08:28:27Z")

</div>

You can use tea command-line tool. `tea issues`.