In this page

Overview
Configuring Excel templates via configuration variables
Creating new Excel templates
General-purpose issue exports
Issues with selected fields
Issues with all fields
Automatic localization
International characters
General-purpose issue exports with additional metadata
Issues with selected fields and comments
Issues with selected fields and worklogs
Issues with selected fields and Tempo worklogs
Issues with selected fields and change history
Created vs. Resolved reports
Created vs. Resolved pivot table
Created vs. Resolved pivot chart
Worklog reports
Worklog pivot table
Worklog pivot chart
Cross-project per-component worklog report
Time in Status & Time to First Response type reports
Time in status pivot table
Time in status pivot chart
Jira Software agile reports
Epic status report
Distribution of Story Points
Sprint size comparison
Learn more about the Jira Software integration
Jira Service Desk reports
Service Desk pivot table
Distribution of Request Types
Average resolution time per assignee report
Learn more about the Jira Service Desk integration
Zephyr test reports
Zephyr test steps
Zephyr test executions
Zephyr test step results
Zephyr test report
Learn more about the Zephyr integration
Tempo reports
Tempo time estimate vs. time spent pivot table
Tempo accounts pivot chart
Tempo teams pivot chart
Learn more about the Tempo Timesheets integration
Insight reports
Issues with objects
Issues with objects and their attributes
Issues per objects pivot chart
Learn more about the Insight integration
nFeed reports
Issues with nFeed fields
nFeed pivot table and chart
Learn more about the nFeed integration
Visual Basic enhanced dynamic reports
Macro executed when opening the XLSX file
Other exports
Jira user accounts

Overview

This gallery displays sample exports created using the "factory-default" templates shipped with the Better Excel Plugin for Jira. Our aim is to give you a quick understanding of what is possible out of the box. This is obviously just the beginning of the story, because the customization and export creation possibilities are literally endless.

You can use the "factory-default" templates in the following ways:

  1. As they are (we polished them further and further over the years so that they give a ready-made solution for most situations)
  2. Configure their look and behaviour by editing their configuration variables (see next section)
  3. Customize their look and behaviour by actually editing the template or the corresponding scripts
  4. Make a copy of them for the starting point of a new template
  5. Use their implementation as "cheatsheet" when developing custom templates

Configuring Excel templates via configuration variables

Many of the templates shipped with the Better Excel Plugin for Jira offer configurability via variables. These variables appear in the top part of the Groovy scripts, and are documented right in the code. Some variables are required to work correctly (like setting up the Tempo authentication for Tempo exports), while some actually modify the export's look or behaviour.

For instance, the Groovy script that connects to Tempo (tempo-tool.groovy) offers the following configuration variables:

tempoApiToken = 'e4f41d78-f8e1-407a-9fba-ccafd2c83d86'
tempoDateFrom = '2000-01-01'
tempoDateTo = '2099-12-31'

You can edit the configuration variables intuitively:

  1. Login to JIRA as administrator.
  2. Go to AdministrationAdd-onsExcel Templates.
  3. Click the template file you wanted to edit, for example tempo-tool.groovy. It opens in the built-in template editor.
  4. Edit the variables.
  5. Save your changes.
  6. Make a new export, which will reflect the changes in the configuration variables.

Creating new Excel templates

You can easily create custom templates by reading the template development documentation and by using the recipes that we collected for frequent use cases.

For those who'd rather focus on their core business and use our expertise to create custom Excel templates for their needs, Midori offers template development services.

General-purpose issue exports sharing customer-facing document archiving

The issue-navigator.xlsx template exports any list of issues from Issue Navigator to straight-forward spreadsheets using the currently configured columns and ordering. It allows you to create custom Excel exports from ad-hoc JQL searches and saved filters with a single click. Please note that each cell is exported with the correct data type (text, number, date, link) and data format (number formats, date formats) automatically, thus there is no need for further manual "post-processing". As for visuals, this one and all our Excel templates apply the "invisible design" paradigm, allowing readers to focus on the data. (Nevertheless you are welcome to customize its look to your own branding and needs.)

Issues with selected fields

This is the most basic, yet the most frequently used export type. Export exactly those columns that you selected in the Issue Navigator to XLSX, the native spreadsheet file format used by Microsoft Excel, Open Office, Google Spreadsheets, Apple Numbers and all standard spreadsheet tools.

jira-issues-selected-fields.xlsx

Issues with all fields

Similarly to the previous one, you can export all issue fields to a spreadsheet that captures the complete state of the issues with one click.

jira-issues-all-fields.xlsx

Automatic localization

This example shows that the template automatically uses the preferred language of the user who created the export, turning the caption Key to Schlüssel or Labels to Stichwörter, for example.

jira-issues-selected-fields-german.xlsx

International characters

All our templates fully support Unicode, i.e. all character sets from Eastern European to Asian. This particular example was created with Japanese locale (Japanese characters and Japanese date format).

jira-issues-selected-fields-japanese.xlsx

General-purpose issue exports with additional metadata sharing customer-facing document archiving

The default template set includes specialized versions of the issue-navigator.xlsx template to export issue metadata (change history, comments, worklogs, Tempo worklogs) along with the actual field values. The specialized templates also support the selected fields and all fields modes, plus the metadata gets exported in the rightmost columns. The metadata values are exported to separate "atomic" columns (e.g. comment author, date and text) and to multiple rows (when an issue have multiple comments) for a structured data layout.

Issues with selected fields and comments

Using the issue-navigator-with-comments.xlsx template, the comments added to the corresponding issue are exported to 3 separate columns (author, submission time and text).

jira-issues-selected-fields-with-comments.xlsx

Issues with selected fields and worklogs

Using the issue-navigator-with-worklogs.xlsx template, the worklogs added to the corresponding issue are exported to 4 separate columns (time spent, author, submission time and comment text).

jira-issues-selected-fields-with-worklogs.xlsx

Issues with selected fields and Tempo worklogs

issue-navigator-with-tempo-worklogs.xlsx is the Tempo-optimized version of the previous template. It integrates with the Tempo time tracking add-on and also exports the account and activity associated for each worklog.

jira-issues-selected-fields-with-tempo-worklogs.xlsx

Issues with selected fields and change history

Audit type of use cases require you to export all fields and their complete change history. Using the issue-navigator-with-history.xlsx template, the changes made on the corresponding issue are exported to 5 separate columns (author, change time, changed field, old- and new value).

jira-issues-selected-fields-with-change-history.xlsx

Created vs. Resolved reports reporting business intelligence

The created-vs-resolved-report.xlsx template exports the creation date and the resolution date (both transformed to year, month and day components using Excel functions) plus several issue fields to its last worksheet. Then it displays multiple pivot tables and pivot charts using various combinations of the project key / issue type / status / assignee / etc. fields in the other worksheets. You can easily clone and customize the template to your needs, by adding, modifying, deleting field values or by adding, modifying, deleting pivot worksheets. The resulted reports are delivered ready-made (no need for further clicks), also working perfectly in automations for periodically updated reporting.

Created vs. Resolved pivot table

This example displays the created vs. resolved counts grouped by project horizontally and grouped by year, month and day vertically. Year, month and day resolution can be expanded / collapsed. Totals are also shown. All these rely on standard Excel features, leveraging the best of Jira and Microsoft Excel.

jira-created-vs-resolved-report.xlsx

Created vs. Resolved pivot chart

This pivot chart visualizes the created vs. resolved counts grouped by projects and years. As for pivot tables, pivot charts also allow you to freely configure its dimensions, grouping or filtering.

jira-created-vs-resolved-report.xlsx

Worklog reports time tracking reporting business intelligence

The worklog-report.xlsx template effectively aggregates the worklogs of the issues resulted by any arbitrary JQL search. This helps to understand the time spent on the issues, projects, issue types, versions, components, etc. grouped and filtered by date ranges, users, etc. This factory default template is also a great starting point to create your ideal time report template.

Worklog pivot table

This example summarizes the time spent by issue type and assignee. You can drill down to year level. Grand totals are available. Even this trivial example should give you a quick demo of the capabilities.

jira-worklog-report.xlsx

Worklog pivot chart

This pivot chart gives you a super-fast overview of work allocation among multiple Jira projects by assignee. Please note the special chart theme (dark background with orange colored 3D bars) applied with a single click.

jira-worklog-report.xlsx

Cross-project per-component worklog report

This is an example of aggregating efforts by components from multiple projects, when your Jira projects have identically named components. As you see, the worklogs can be collected from any arbitrary issue list, i.e. your scope is not limited to projects or to any kind of container.

jira-worklog-report.xlsx

Time in Status & Time to First Response type reports SLA reporting business intelligence

The workflow-report.xlsx template calculates various time metrics from Jira data: Time in Status X (for each status), Time to First Response, Time to Resolution, etc. Then it offers average and totals in the form of pivot tables and pivot charts, to understand the lifecycle of your issues and the performance of your team or service. In addition to customizing the pivot tables and charts, there are many ways to customize the underlying data itself. For instance, you can add your own time metrics by modifying the workflow-report.groovy script. Or, you can add your own SLA's by adding comparison formulas to the Excel template, like if priority is Critical and Time to Resolution is less than 4 hours, then the SLA is met, otherwise breached. It's all up to you!

Time in status pivot table

This simplistic example shows the average time spent in various statuses and the time required for the resolution per issue type. Grand totals are displaying the total averages for both dimensions.

jira-workflow-report.xlsx

Time in status pivot chart

This pivot charts makes the numbers in the previous pivot table faster to grasp using a bar-type pivot chart.

jira-workflow-report.xlsx

Jira Software agile reports scrum reporting kanban

Better Excel Plugin fully integrates with Jira Software, the Jira edition custom tailored for software engineering teams. Jira Software specific custom fields (Sprint, Epic and Story Points) are exported to Excel, in addition to the general data. The Excel Export menus are seamlessly integrated to the Jira Software screens: to the Backlog view (to export one specific sprint or the backlog) and to the Scrum and Kanban boards (to export the issues in one column). All in all, this allows you easily extending the built-in Jira Software reports with custom ones, even across projects, across sprints and calculated from arbitrary JQL queries.

Epic status report

Story point distribution among epics, colored by the states of the issues in that epic. This stacked bar chart both indicates the relative sizes of the epics and their current progress status. It is just one example of the unlimited aggregations you can create using various fields (both Jira Software specific and general ones).

jira-agile-report.xlsx

Distribution of Story Points

Story points are visually totaled by issue status and among developers. This gives a quick answer to the most frequent questions of how much work is assigned to, being worked on and competed by each developer?

jira-agile-report.xlsx

Sprint size comparison

This one-dimensional pivot pie chart compares the relative sizes of multiple sprints. It aims to ensure that the work assigned to sprints is realistic, without major deviations from the team's average velocity.

jira-agile-report.xlsx

Learn more about the Jira Software integration

See the Jira Software section in the Integrations page for a tutorial video and technical details.

Jira Service Desk reports ticketing sla reporting business intelligence

Jira Service Desk is the fastest-growing application developed by Atlassian on the top of the Jira platform. Not only the Service Desk managed custom field types (like SLA or Request Type) are supported the Better Excel Plugin, our add-on also integrates its Export drop-down menu to the Queue, the most important screen in Service Desk. That allows exporting the tickets in that queue to custom Excel reports with one click.

Service Desk pivot table

The jira-service-desk-report.xlsx template gives several ready-to-use pivot table reports. This example displays the number of tickets per project, per request type and per status. There are additional pivot tables for assignees, ticket participants, etc., and as always, you are welcome to add your own!

jira-service-desk-report.xlsx

Distribution of Request Types

For most pivot tables in the jira-service-desk-report.xlsx template, there exists the corresponding pivot chart, to make the results easier to understand. This example shows an intuitive report of the issue types (main category) and the request types (sub-category) per project.

jira-service-desk-report.xlsx

Average resolution time per assignee report

Still in the jira-service-desk-report.xlsx template, you can create flexible reports on the SLA type custom fields. One of the most typical examples is the report that visualizes how fast each agent solves his or her own requests.

jira-service-desk-report.xlsx

Learn more about the Jira Service Desk integration

See the Jira Service Desk section in the Integrations page for a tutorial video and technical details.

Zephyr test reports test management testing reporting

Better Excel Plugin integrates with Zephyr, the most popular test management add-on for Jira. Zephyr tests are "first-class citizens" in the Better Excel Plugin exports, meaning that similarly to Jira issues you can export all test related information to Excel: test details (fields, attachments, comments, etc.), test steps, test executions and detailed step results during an execution. Also, you can use all Excel reporting and analytical features on Zephyr data, from functions and formulas to pivot tables and pivot charts.

Zephyr test steps

Zephyr test definitions are issues of the "Test" type. This example generated from the issue-navigator-with-test-steps.xlsx template shows a mix of regular issue fields in the left (key, summary, priority) and test step details in the right (instructions, test data, expected result).

jira-zephyr-test-steps.xlsx

Zephyr test executions

Easy and flexible: run a JQL search to find any arbitrary set of tests, then generate a filterable, searchable, shareable, grouped list of all test executions.

jira-zephyr-test-executions.xlsx

Zephyr test step results

This highly detailed Excel export captures the test results in three logical levels: tests, test executions for each test, and test step results for each execution. Being a complete snapshot of testing data, you can search this, import this to external systems, use it for archiving purposes, etc.

jira-zephyr-test-step-results.xlsx

Zephyr test report

You can also create powerful reports from Zephyr test data. The zephyr-report.xlsx template gives a valuable overview of test executions per version, test cycle and tester, shows the test execution history, and shows which tests and executions discover the most defects. Build your own Zephyr Excel report by copying this template.

jira-zephyr-report.xlsx

Learn more about the Zephyr integration

See the Zephyr section in the Integrations page for a tutorial video and technical details.

Tempo reports time tracking reporting business intelligence

Integration with the popular third party add-ons is a key goal for the Better Excel Plugin team, in order to create more value from your previous investments. In our concept, there is no difference between Jira-internal data or third party add-on data for the end-user. Tempo is the most widely used time tracking add-on for Jira, therefore the Better Excel Plugin seamlessly integrates with Tempo.

Tempo time estimate vs. time spent pivot table

The tempo-report.xlsx exports the high level Time Estimate and Time Spent values augmented with the Tempo managed data (Account, Iteration, Team) for each issue. It offers various pre-configured pivot tables, or can be cloned to create your own Tempo reports.

jira-tempo-timesheets-report.xlsx

Tempo accounts pivot chart

Account is a concept specific to Tempo, yet fully supported by the Better Excel Plugin. This pivot chart example features an aggregation using the account field managed by Tempo.

jira-tempo-timesheets-report.xlsx

Tempo teams pivot chart

This an another example of using Tempo managed data, in this case teams, in an Excel report.

jira-tempo-timesheets-report.xlsx

Learn more about the Tempo Timesheets integration

See the Tempo Timesheets section in the Integrations page for a tutorial video and technical details.

Insight reports reporting business intelligence asset management

Insight is the leading asset management add-on for Jira, that allows implementing CMDB, CRM, HR, ITSM or ITIL functionality on the Jira platform. Better Excel Plugin is tightly integrated with Insight, allowing you to export all Insight custom fields with the desired granularity (object keys, names and attributes) to Excel. Having full access to Insight objects and their attributes, you can easily implement custom reporting and Business Intelligence on Insight data.

Issues with objects

This straightforward Excel export (created using the default issue-navigator.xlsx template) contains two Insight custom fields: one of them is single-select, while the other one is multi-select type. Both use the "object name [object key]" format.

jira-insight-export.xlsx

Issues with objects and their attributes

This example is configured to export the complete attribute set for each Insight object. Attributes are exported as comma-separated name-value pairs in brackets (the format is completely customizable).

jira-insight-export-objects-with-attributes.xlsx

Issues per objects pivot chart

You can also create custom reports with Insight data, just like with any other built-in custom field. The insight-report.xlsx template calculates issue count per object, project distribution per object and status distribution per object. Look for more? Create your own Insight Excel report using this template as a starting point.

jira-insight-report.xlsx

Learn more about the Insight integration

See the Insight section in the Integrations page for a tutorial video and technical details.

nFeed reports reporting data integration business intelligence

The nFeed add-on integrates external data sources (SQL databases, LDAP, Active Directory, REST APIs, Salesforce, CSV files, etc.) to Jira. Better Excel Plugin is tightly integrated with nFeed, allowing you to export all nFeed custom fields to Excel via a configurable transformation. More than data export, you can easily implement custom reporting and Business Intelligence on nFeed data.

Issues with nFeed fields

This straightforward Excel export (created using the default issue-navigator.xlsx template) contains several nFeed custom fields: one of them is a Google Drive document selector, while customers, invoice address and contacts are dependent fields loaded from an external CRM database.

jira-nfeed-export.xlsx

nFeed pivot table and chart

Create custom reports with nFeed fields just like with built-in custom fields. This report example merges Jira issues (consulting tasks) with customers' data in an external CRM database, and gives various pivot tables and pivot charts based on those.

jira-nfeed-report.xlsx

Learn more about the nFeed integration

See the nFeed section in the Integrations page for a tutorial video and technical details.

Visual Basic enhanced dynamic reports reporting

Exported XLSX files does not need to be static. Certain use cases may require you to add dynamic logic for dynamic post-processing, for interactions and for other purposes. The add-on fully supports Visual Basic (VBA), the native scripting language of Microsoft Excel, to meet those requirements.

Macro executed when opening the XLSX file

This example is essentially the illustration for our VBA tutorial article. After the XLSX was exported from Jira, every time when you open this, it executes a little VBA macro that turns the overdue issues to red, and also displays their count in a message box. (Overdue issues are the unresolved issues that have their due date already passed.) This simplistic example demonstrates the concept of using VBA to create dynamic reports.

Other exports data integration data analysis archiving

The Better Excel Plugin enables working not only with issues, but with any kind of data. Our motto: if the data is available in Jira or from external data sources; template customization, Excel features, Groovy scripts, Visual Basic macros allow extracting insights from those in any scenario. This section shows examples of exporting information not strictly related to issues.

Jira user accounts

The user-export.xlsx template exports user accounts to Excel, including username, last login time, login count, failed login count, group memberships, roles and more. This is a particularly useful in large Jira instances to find the unused seats and garbage among thousands of user accounts, with Excel sorting and filtering.

jira-user-export.xlsx