Export issues from Jira are one of the features that make the tool more powerful, chiefly because it offers the exemption to work with external tools for a variety of function cases ; possibly you need to know how to extract data from Jira using API or doing a Jira XML export, or possibly you need to make Jira Service Management ( once Jira Service Desk ) exports to Excel. It will depend on your needs, and we will cover different scenarios and solutions in this military post.
Although each case is unique at the time to export issues from Jira, it’s handy to create Jira reports outside Jira, Jira audits, analyzing SLAs, performing Jira migrations, and more .
After a couple of years of this post being published and following a recommendation from our Twitter community, we got hands-on to update this guide to export issues from Jira. This was the conversation that motivated us ( You can always follow us there, excessively 😉 ) :

data from 2018 … I believe that since then, there are new options such as a native Excel plugin that allows issues to be downloaded directly into Excel. besides, I think there were changes in the way to download via API, not then sure on that … possibly article could be updated

Reading: 8 Ways to export issues from Jira in 2021

— Angel Lampreave (@alampreave) September 1, 2020

When Jira issues are filled with information, they give detail information. Given the coarseness each return contains, it fits perfectly into an Excel spreadsheet, where each consequence occupies a row and each field a column. Hence, exporting issues from Jira is a must when working with this information outside the cock .

Why export issues from Jira ?

Users have said they export Jira issues chiefly because they need to treat information differently from what Jira offers. therefore, we ‘ll show everyday situations that motivate people to export this datum from Jira. Later on, we ‘ll discuss different ways to export issues and their contents .
Share information with external people : It’s usual for clients to request detail reports in different formats, broadly Excel, CSV, or PDF .
Analyze data in Excel: Given the management staff, it ‘s normally identical skilled within Excel, exporting detailed information from each Jira emergence is helpful to understand the data and produce reports there .
Audit Jira information: It’s potential to audit your case directly in Jira. however, this implies investing in hours of training on Jira. If that would be the case, your auditor should :

•    Know how to use Jira.
•    Have Jira Administrator privileges.
•    Learn to find and collect the information needed from Jira dashboards and reports.

This highlights the dim-witted benefit of exporting the naked data and letting them explore at their own pace with the tools they master ; it ‘s normally the best way to go .
Analyze SLA compliance: When managing service delivery in Jira, it ‘s common Service Managers or customers need to get statistics about their SLAs, and sometimes, the Jira coverage engine may fall short for such a undertaking. consequently, it ‘s normal to look for reporting alternatives in the Atlassian Marketplace such as eazyBI and/or export the issues to CSV, PDF, or Excel to analyze the complaisance of their SLAs .
Migrate issues between Jira instances: It’s possible to natively import issues to a unlike Jira exemplify with a CSV archive, which is specifically utilitarian when partial migrate issues between instances ; To do this, previously will be necessity to export these issues CSV to import them into the target example late. The relationship between the beginning and finish environments would be the follow :

•    From Jira Data Center to Jira Cloud.
•    From Jira Cloud to Jira Data Center.
•    Between similar environments. 

How to export issues from Jira ?

In essence, exporting issues from Jira, it ‘s very straightforward ; it requires three basic steps :

1. Select the issues you need to export from Jira.
2. Search for the export button located at the Issues Navigator menu.
3. Select the format in which you want to export the issues.

Despite how easy it seems to export these issues from Jira, it ‘s besides true there are several limitations, particularly when exporting the wide message each issue contains :

Which additional content can be exported from Jira issues to Excel?

• Jira Cloud: It’s possible to export more than a thousand issues natively. To export transitions and comments, get Exporter for Jira from the Atlassian Marketplace .
• Jira Data Center (or Server): It’s possible to export more than a thousand issues by modifying the properties file -below, we explain how-. To export transitions, comments, and attachments, you need It’s potential to export more than a thousand issues by modifying the properties file -below, we explain how-. To export transitions, comments, and attachments, you need exporter from Jira

Which additional content can be exported from Jira issues to CSV?

•    Jira Cloud: You can export the comments of each Jira issue to CSV natively. To export more than 1000 issues, the history of issue transitions, and opt to change the delimiter (dot, semicolon,…), you will need Exporter for Jira.
•    Jira Data Center (or Server): It’s possible to export comments, change the delimiter (point, colon, semicolon…), and export more than 1000 issues natively; this last option can be done by modifying the Jira properties file. Exporter for the Jira does the same, besides exporting the history of the transition.

Limitations when exporting Jira issues

These limitations may vary ; it depends on whether you’re in Jira Cloud or Jira Data Center, as we have shown. In the comply, we ‘ll explain more about these limitations ; there are three :

1. Jira does not allow exporting issues from Jira to Excel, or PDF: It’s not possible to export issues to Excel from Jira Data Center ; on the other hand, it allows exporting issues to Word formats and CSV, which changes in Jira Cloud; it enables opening Jira issues in Google Spreadsheets or Microsoft Excel 365. It’s amazing!
   How to export Jira issues to Excel? Well, we love this Jira Cloud feature of opening issues in Google Spreadsheets.
2. Jira does not export all the content from Jira issues: The native exports from Jira issues usually omit critical data such as transitions, comments, or the attachments of each issue.
3. It is not possible to export more than one thousand issues from Jira in the same action: Although Jira Cloud allows it (only when exporting to Excel) with the option we pointed at first (opening issues in Google Spreadsheets), in Jira Data Center, it’s not possible to do so by default; Installation level changes and a system reboot are required to enable this option. In the following list, we’ll tell you how to do it:

Export plan information from Jira Cloud to Power BI > >

8 Ways to export issues from Jira

Let ‘s go through the eight most common ways to export issues from Jira, motivated by some, all, or none of the reasons we discussed earlier.

The two first alternatives are meant to be performed by even users ( it does n’t require much tech cognition ), and the six remainings are by and large targeted at Jira Administrators .
We want to know your perspective ! As you have seen already, we ‘re all ears. Contact us, write it in the comments, or reach us on social media if you have something to add .

1. Export issues from Jira using the “Export” button located in the Issue Navigator

This is one of the easiest options to perform, as we explained before. Likewise, it has the limitations besides stated :
There are no native exports to Microsoft Excel in Jira Data Center, and merely up to 1000 issues can be exported. In Jira Cloud and Jira Data Center, it ‘s impossible to export issues with attachments, comments, or transitions. If you are felicitous with the result, you should probably embrace it ; there ‘s no argue to reinvent the rack .
Take a look at the Atlassian documentation on the different nonpayment export formats : you can export to Word and/or CSV ; Export Jira issues to XML is handy for developers who want to process data .

2. Export Jira issues with an Atlassian Marketplace app

Finding the app that best suits you requires exhaustive research make on each possible option available in the Atlassian Marketplace .
Given the ignorance of the options available within the market, which in most cases represents the easiest way to add functionality to the Atlassian tools ( Jira, in this case ), counting on the aid of Atlassian Certified Professionals for this tax -although it may involve extra investment- will save you respective headaches, since Atlassian apps do not require care or compatibility with the most late versions of Jira .
Among the most popular options, there ‘s Xporter for Jira, which allows you to customize how the information is exported visually. On the early hand, Exporter for Jira will enable you to overcome the limitations of Jira in terms of the number of issues to export or the accomplished data of the consequence in utilitarian formats. There are besides general applications that allow it, such as the Jira CLI, which is more complex and useful for advanced data processing.

From nowadays on, to understand the watch options, you ‘ll need more in-depth technical school cognition, thus do n’t take it as a rigorous recommendation of what you should do .
If you’re not certain to understand any of the postdate solutions, do n’t do it ! It could work, or it could create more significant problems. In any case, all the elements to be mentioned are real solutions because people are doing it :

3. Modify the Jira properties file to export issues (Only for Jira Data Center or Server)

There are three ways to export issues from Jira following this path :

3.1. Reactivate the Excel export option from the Jira menu

This option allows having the Excel export choice available from the Exports drop-down menu.

note, the “ Excel document ” that Jira will export is an HTML document that can be outdated at any moment. Any process depending on this configuration may have to change when Atlassian stops supporting this export mechanism .

How to reactivate issue exports to Excel from the Jira menu?

Remember to perform this natural process at off-peak hours since the follow steps require to stop the arrangement :

•    Stop Jira.
•    Go to the directory and find the file jira-config.properties
•    If the file does not exist, as will be the case for new Jira installations, go ahead and create it.
•    Edit the file (follow these instructions if you are not familiar with the process) and add the following parameter on a new line:
  jira.export.excel.enabled=true

•    Save the configuration file, and close it.

•    Restart Jira.

•    Share it with your team.

3.2. Increase the limit of the property to 1000 results per search

Although it ‘s a simple configuration that works like the previous one, it does n’t solve the issues ‘ limitations in formats and content. This configuration will besides require stop and restart Jira.

Atlassian suggests doing large exports in batches to avoid out-of-memory exceptions. If you’re correctly monitoring the performance of your Jira example, and you’re comfortable testing the limits without blocking the tool, or if you have besides many issues with adopting the batch approach, you can change the export specify of 1000 issues from the properties file :

How to surpass the limit of the property to 1000 results per search?

•    Stop Jira.
•    Go to the directory > and find the file jira-config.properties
•    Edit the file with the new desired maximum [new max]:
•    jira.search.views.default.max=[new max]
•    Restart Jira.
•    Share it with your team.

3.3. Surpass the limit of the property to 1000 results per search (for certain users)

This option privilege a small group of Jira users to overcome the property that limits exports to 1000 issues each time. This shape requires stopping and restart the tool .
The issues to be exported will be the ones filtered in the consequence browser at that meter. Ensure the group of users with access to these exports understand the province it implies, and they are aware of how it will affect the case ‘s performance .
Depending on who is exporting and for what aim, you may want to remove Jira Administrators ‘ limitation, i, the IT directors of your company .

How to bypass the Jira export limit for a selected group of users?

•    Stop Jira.
•    Go to the directory > and find the file jira-config.properties
•    Edit the file with the new limit for administrators:
•    jira.search.views.max.unlimited.group=jira-administrators
•    Restart Jira.
•    Share it with the team that has this special permission and explain the following in an email:
  •  To exceed the limit, Jira administrators can edit the URLs.
  •  Copy the search URL into the issue navigator.
  •  Paste it on a new tab.
  •  Edit the max parameter at the end or remove it entirely to get the full results.

4. Export more than 1000 issues to CSV from Jira Cloud

deoxyadenosine monophosphate hanker as we refer to CSV exports, Atlassian shares this alternative as a solution for Jira Cloud instances regarding the exports for more than 1000 items .
Suppose you are exporting from Jira Cloud to Microsoft Excel. In that character, Atlassian allows that antic choice to open Jira issues immediately in Google Spreadsheets or Excel, and from there, to open more than 1000 issues .

5. Export Jira issues for migration or backup purposes

Suppose you are carrying out a backup or a migration march. In that case, this is the best choice since creating a stand-in with the information of your exemplify will get a massive bach of information … everything you have in your Jira, including the attachments of each issue. here are the full instructions Atlassian offers for these scenarios.

Obtaining the stand-in file is simpleton. The slippery contribution is to extract only the issues from the entity.xml file, where the projects, users, groups, components, etc., coexist. If you’re interest in getting all the information about just the issues, you ‘ll have to dig into the XML file to get them. That ‘s arduous work !

6. Export Jira issues with the Java API

This choice will allow you to set up the outputs as you wish before exporting the issues ; If person on your team is familiar adequate with Java development, it ‘s an excellent option to pass the JQL question through the Java API. You will speak to Jira in its original language :

How to export Jira issues via Java API?

The question for versions previous to Jira 8 :
String jql="assignee=currentUser()"; SearchService.ParseResult parseResult = searchService.parseQuery(applicationUser, jql); if (parseResult.isValid()) { try { /** * Execute the search and get the issues */ List issues = searchService.search(applicationUser, parseResult.getQuery(), PagerFilter.getUnlimitedFilter()).getIssues(); }catch (SearchException ex){ LOGGER.error("Error searching: ",ex); } } else { LOGGER.error("Error parsing: " + parseResult.getErrors()); }
The question for Jira 8 versions onwards :
String jql="assignee=currentUser()"; SearchService.ParseResult parseResult = searchService.parseQuery(applicationUser, jql); if (parseResult.isValid()) { try { /** * Execute the search and get the issues */ List issues = searchService.search(applicationUser, parseResult.getQuery(), PagerFilter.getUnlimitedFilter()).getResults(); }catch (SearchException ex){ LOGGER.error("Error searching: ",ex); } } else { LOGGER.error("Error parsing: " + parseResult.getErrors()); }
Download the full moon .java snip for previous Jira 8 versions, and here for Jira 8 versions onwards, given it has changed getIssues ( ) to getResults ( ) from the Jira 8 adaptation onwards. This code includes authentication and imports. Just add a class and a method to make the call .

7. Export Jira issues through the REST API

This Jira export API option is simple and answers the central question: How to extract data from Jira using API? The suffice is straightforward ; with it, you ‘ll get a JSON output charge, although the results can not be shared immediately ( Same as the previous Java API exemplar ).

Following the GET method acting of the REST API, once you ‘ve logged into Jira, you ‘ll be able to retrieve all the issues using a particular JQL from a url :

 Method: GET 
 Url: JIRA_BASE_URL/JIRA_CONTEXT/rest/api/2/search?jql="assignee=currentUser()" 

paste this URL directly into your network browser for on-screen results ; alternatively, you ‘ll credibly preferably use an API development environment like Postman or a command-line tool like Curl.
Something to avoid is looping through the resulting JSON as a exploiter.

If you are looking for the Excel Jira REST API, to give you an idea, here ‘s a screenshot with the begin of the datum of an issue and how it ‘s displayed :
Example of how the data of an emergence looks when exporting it with the Jira Rest API .
… and it goes like this for even other 86 lines .

8. Export all the content from Jira issues: Comments, attachments, and transitions

There are ways to export Jira issues, as you might see. Besides, several options available in the Atlassian Marketplace take the export of Jira data to another level ; the solution you ‘ll choose will depend on your needs .
Suppose your need relies on auditing tasks, analyzing SLAs, making Jira reports outside the tool, etc. In that case, you ‘ll need to export comments and transitions from either Jira Cloud or Jira Data Center ( or Server ) with Exporter for Jira .
On the other handwriting, if you’re considering migrating from Jira Server to Jira Cloud, this is a valuable option to extract data from Jira and move your information from one instance to another. This can be done with Exporter for Jira Data Center ( or Server ) by exporting Jira publish attachments.

Finally, if you need to create instant internal reports for team meetings, exporting issues to PDF, both in Jira Cloud and Data Center ( or Server ), is the way to go, and Exporter for Jira does it for you .

8.1 Automate issue exports delivered to your email inbox 

If you need to run issues exports sporadically and you do n’t want to keep atrophy fourth dimension by setting up the information you need to export every time, by choosing which column, selecting the format, choosing if you besides need to export the comments and transitions, etc, the late BETA have of Exporter for Jira Cloud might help you on this .
The schedule Exports is the latest feature for the app entirely in Cloud, allowing users to plan the frequency to download a specific export of Jira issues and besides allows you to save the download settings .
On the chosen day, you will receive an e-mail in your mailbox with a link to download the file back to Jira. It will besides be possible, right from the top menu of Jira, in the Apps drop-down menu, to see the details, manually run the export, edit parameters, or delete any or delete them if you no longer need them.
Have in mind, your Jira Administrator will need to perform a previous configuration filling the details of your e-mail server in the Exporter sub-menu, located in the Jira administration empanel.

This is a solution available in the Atlassian Marketplace. Avoid the human erroneousness divisor, and start configure and automating the delivery of your Jira Cloud issues to your e-mail inbox, and exporting right from Jira ; this solution guarantees you will constantly have the same shape of your issues export available to download it at any time you need.

ultimately, whatever the choose method acting, once the data is extracted from Jira, the dilemma relies on which discussion will remove that data .
Before going through, it ‘s crucial to reflect on : Is it indispensable to have this information outside Jira for reporting purposes ? Nowadays, Jira Software and apps offer unlike ways to create and export reports, flush at the undertaking degree, mighty from the creature, without processing the data outside the Jira. Whichever option you choose, we hope it will be beneficial for you .