Documentation for JIRA 5.2. Documentation for other versions of JIRA is available too.

JIRA enables you to easily export your search results from the Issue Navigator to Microsoft Excel. This can be a useful way to format data and create your own customised reports, graphs and charts.

Related topics:

Exporting to Microsoft Excel

Before you begin:

  • Large exports (e.g. many hundreds of issues) are not recommended.
  • To change the number of issues that are exported, change the value of the tempMax parameter in the URL.

To export search results to Microsoft Excel:

  1. Choose Issues > Search for Issues.
  2. Refine your search, as described in Searching for Issues, then choose the eye icon .
  3. Choose one of the following from the dropdown menu:
    • 'Excel (All fields)'— this will create a spreadsheet column for every issue field (excluding comments).
      • Note: This will only show the custom fields that are available for all of the issues in the search results. For example, if a field is only available for one project and multiple projects are in the search results then that field will not appear in the Excel document. The same goes for fields that are only available for certain issue types.
    • 'Excel (Current fields)' — this will create a spreadsheet column for the issue fields that are currently displayed in your Issue Navigator.
  4. A file called <My company's JIRA> - <My project>.xls will be created. Edit this file using Microsoft Excel and/or save it as required.

Here is a sample exported file, viewed in Microsoft Excel:

 

3 Comments

  1. Anonymous

    Dec 26, 2012

    Currently it exports "original estimate" by seconds, how can we get the excel by days?

    1. SusanA

      Jan 02, 2013

      Your best place for answers and support is one of these two sites: https://support.atlassian.com/ or https://answers.atlassian.com/.

  2. Charles W

    Jun 19, 2013

    We were previously able to export more than 1000 issues by altering the variable in the JQL URL, however, we're now receiving "Forbidden 403 messages". Is there a way we can regain the previous functionality?



See our Getting Help page for details.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.