What is the best way to export all JIRA data (projects, issues, ...)? I saw that there is an API and a plugin mechanism which probably can provide all the information. But what is the easiest way to export the data? Does it work out of the box or do I have to implement a plugin?
相关问题
- Set assignee field when creating an issue in JIRA
- How to serialize a jira issue object in Python?
- How can I fetch (via GET) all JIRA issues? Do I go
- JIRA: How to make a webhook fire for only a single
- Exporting Comments from Excel
相关文章
- Public issues in JIRA
- TFS vs. JIRA/Bamboo/SVN [closed]
- boost serialization and register_type
- BASH: Is “export” needed, when setting a variable
- Cannot export data to a file in R (write.csv)
- More Efficient Way of making multiple objects
- Flask button to save table from query as csv
- Exporting Excel Charts as Images
I'm using JIRA v1000.747.1 which has native export to CSV of issues.
If you navigate to https://[your-jira-instance]/issues you should see a query screen with results. Fine tune that via the UI or go to the Advanced menu to do more complicated JQL. Then you can click the export button (upper right) to export to XML/Word/HTML/CSV.
The following add-ons will work out of the box, they are configurable and there is no need to code anything:
You can use both free for 30 days, which should be sufficient to migrate your data to the new issue tracker.
You can use this web application to export the data to Word:
http://www.jiratoword.com/
It is quite basic and it could be improved but it is free.
I have written a little ruby utility that uses JIRA's REST API to export all tickets for a given project to the local file system. It is available as a ruby gem, so the installation is trivial.
The tickets are saved as individual JSON files. The tool also supports incremental updates.
Generally, there are two main approaches to backup your JIRA data. The first one is to back up your database in which JIRA info is stored. The second one is to use the “Backup Data to XML feature”, which is a JIRA feature. Personally, I prefer the second one, because it can be restored to any database engine (MySQL, MSSQL, etc). In addition, as far as it is Xml, it can be compressed to a great extent.