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
General-purpose issue exports with calculated fields
Issues with built-in calculated fields
Issues with custom calculated fields
Learn more about the calculated fields integration
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
Bitbucket development report
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
Tickets with customer satisfaction (CSAT) details
Learn more about the Jira Service Desk integration
Portfolio for Jira reports
Portfolio plan scope
Portfolio plan report
Portfolio resource cost report
Learn more about the Portfolio for Jira 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
ScriptRunner exports
Issues with built-in (picker) script fields
Issues with built-in script fields
Issues with custom script fields
Learn more about the ScriptRunner integration
Xray reports
Xray tests
Xray test sets
Xray test plans
Xray test executions
Xray test runs
Xray test report
Xray test run report
Learn more about the Xray integration
Structure exports
Requirements specification
Portfolio report (program report)
Dynamic task list
Learn more about the Structure integration
Insight reports
Issues with objects
Issues with objects and their attributes
Issues per objects pivot chart
Learn more about the Insight integration
Git Integration reports
Issues with selected fields and Git commits
Development task list with Git branches
Git development metrics report
Learn more about the Git Integration integration
Elements Connect (nFeed) reports
Issues with nFeed fields
nFeed pivot table and chart
Learn more about the nFeed integration
Jira Misc Custom Fields (JMCF) exports
Issues with JMCF custom fields
Stories with the most defects report
Low-effort high-impact stories report
Learn more about the Jira Misc Custom Fields integration
Profields exports
Issues with Profields custom fields
Projects with Profields custom fields
Profields project report
Learn more about the Profields integration
Time to SLA exports
Issues with Time to SLA fields
Learn more about the Time to SLA integration
Color Custom Fields exports
Issue list with Color Custom Fields
Learn more about the Color Custom Fields integration
Visual Basic enhanced dynamic reports
Macro executed when opening the XLSX file
Other exports
Jira projects
Jira user accounts
Complex project status report

Overview

This gallery displays sample exports created using the "factory-default" templates shipped with the Better Excel Exporter 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 Exporter 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 app 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

General-purpose issue exports with calculated fields scripted fields calculated fields

In addition to field values, you can easily export calculated values that are not present as issue fields, but should be calculated dynamically at the time the Excel export is being created. Better Excel Exporter ships with several built-in calculated fields that you can use without customizing any template or writing any script. Or, you can dive in and define your custom calculated fields without much technical knowledge!

Issues with built-in calculated fields

This example shows the usage of three built-in calculated fields that come with Better Excel Exporter: Last comment date, Last commenter user and Last comment text. These values are transparently collected by the app by checking the issue comments while creating the Excel file. Just add the corresponding columns to the Issue Navigator and it will work!

jira-issues-with-built-in-calculated-fields.xlsx

Issues with custom calculated fields

New calculated fields can also be added to implement the custom calculations you need. This Excel report contains three custom calculated fields in the columns H-J. For example, Time to Resolution is the time between the creation and the resolution of the issue, made visual and intuitive with conditional red-green coloring. No need for expensive scripting apps!

jira-issues-with-custom-calculated-fields.xlsx

Learn more about the calculated fields integration

See the calculated fields page for a tutorial video and configuration guide.

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 agile

Better Excel Exporter fully integrates with Jira Software, the Jira edition custom tailored for software engineering teams. First, Jira Software specific custom fields (Sprint, Epic, Story Points and Development) are exported to Excel. Second, 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

Bitbucket development report

This development overview report contains user stories, bugs, development tasks with their base fields plus the development information for each. The development information is automatically loaded from the Bitbucket Server, Bitbucket Cloud and GitHub instances linked to Jira. The development information includes the number of branches, the number of commits, and the number and status of pull requests related to the given issue.

bitbucket-development-report.xlsx

Learn more about the Jira Software integration

See the Jira Software page for a tutorial video and configuration guide.

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 by Better Excel Exporter, our app 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

Tickets with customer satisfaction (CSAT) details

Creating customer satisfaction reports in Excel can help you better understand your customers and your service quality. The customer feedback data collected by Jira Service Desk can be exported to Excel either with the satisfaction score only (a number between 1 and 5) or with the score plus the customer's comment. This is a sample for the latter.

jira-service-desk-tickets-with-customer-satisfaction.xlsx

Learn more about the Jira Service Desk integration

See the Jira Service Desk page for a tutorial video and configuration guide.

Portfolio for Jira reports reporting project portfolio management roadmap

Portfolio for Jira is Atlassian's Project Portfolio Management (PPM) solution, an agile roadmapping and project planning app for Jira Software. It helps project managers see the big picture by combining multiple projects and resources on a single timeline. Better Excel Exporter exports the Portfolio custom field values, including Target Start Date, Target End Date, Team, Parent Link and Original Story Points, to Excel. Using the power of JQL, you can create custom reports from the complete portfolio, from multiple programs, from multiple plans, from multiple plan levels, or all these combined!

Portfolio plan scope

This sample is the export of a plan built with Portfolio, including Initiative, Story and Task type work items (issues). It is exported from Issue Navigator using a custom column configuration, which includes all Portfolio-managed custom fields plus Epic Link.

jira-portfolio-export.xlsx

Portfolio plan report

Create custom reports from Portfolio for Jira data. This example compares the logged hours and estimated hours to calculate a progress rate by Initiative (the highest issue level in our example).

jira-portfolio-report.xlsx

Portfolio resource cost report

Similarly to the previous example, you can build a Project or Resource Cost Report. In this example we exported a the dollar value of the work performed on each Epic by Teams and used the Excel pivot chart feature to automatically calculate Resource Cost Report.

jira-portfolio-report.xlsx

Learn more about the Portfolio for Jira integration

See the Portfolio for Jira page for a tutorial video and configuration guide.

Zephyr test reports test management testing reporting

Better Excel Exporter integrates with Zephyr, the most popular test management app for Jira. Zephyr tests are "first-class citizens" in the Better Excel Exporter 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 page for a tutorial video and configuration guide.

Tempo reports time tracking reporting business intelligence

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

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 Better Excel Exporter. 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 page for a tutorial video and configuration guide.

ScriptRunner exports scripted fields reporting calculated fields

ScriptRunner is the most powerful app to extend and customize Jira with every kind of custom logic, programmed in Groovy scripts. Among other extension points, you can implement custom fields with it, whose values are programmatically calculated or automatically loaded from external databases, APIs or other sources. Better Excel Exporter allows exporting all those script fields to Excel spreadsheets, including both the ones powered by built-in and by custom Groovy scripts.

Issues with built-in (picker) script fields

This is an example with a selection of the ScriptRunner-managed "picker" type custom fields: Issue picker, Remote issue picker and Database Picker (in the columns H-J). Better Excel Exporter supports all the single- and multi-valued "picker" variants.

jira-scriptrunner-export.xlsx

Issues with built-in script fields

ScriptRunner offers script fields which are powered by ready-made scripts shipped with the app, which therefore work without any programming. In this sample, these are exported to the columns H-J, automatically translated to Excel cells using the correct data types (date, number, etc.).

jira-scriptrunner-built-in-script-fields-export.xlsx

Issues with custom script fields

In addition to the built-in script fields, ScriptRunner enables you to create script fields that are powered by custom Groovy scripts written by you. All you need to do is properly configuring those with a searcher, Better Excel Exporter will find out their data types and your custom field values will be correctly exported to Excel! Zero extra work required.

jira-scriptrunner-custom-script-fields-export.xlsx

Learn more about the ScriptRunner integration

See the ScriptRunner page for a tutorial video and configuration guide.

Xray reports test management testing reporting

Xray is a complete, end-to-end test management app for Jira. It supports the entire testing and quality assurance lifecycle: test planning, test design, test execution and test reporting. Better Excel Exporter exports all test-related information, including all Xray-specific entities and all Xray-specific custom fields, to Excel. It enables sharing test data with stakeholders, migrating test data to external systems, and most importantly creating every type of custom reports from test data.

Xray tests

Xray stores most of the information in its specific custom fields, all supported by Better Excel Exporter. This example is an export of Xray tests, generated from the columns selected in Issue Navigator, including the test key, summary, test steps, plus the pre-conditions, test sets and test plans associated with the given test.

jira-xray-tests-with-test-steps.xlsx

Xray test sets

Test sets are flat, ordered collections of tests, represented by their own Xray-specific issue type in Jira. This Excel export lists test sets with their contained tests and the status of those. Tip: to analyze the Test Set Status cells, convert those to multiple cells using Excel formulas.

jira-xray-test-sets.xlsx

Xray test plans

In this Excel spreadsheet, you can see the list of the test plans which collect the tests to be validated against a specific product version or within a specific sprint, their schedule, and the respective results. You can easily filter the list to any given period by using the standard Filter feature in Excel on the Begin Date and End Date columns.

jira-xray-test-plans.xlsx

Xray test executions

Test executions are assignable tasks for executing a group of tests against a specific system revision (version) in a specific environment, as a part of the testing plan. This Excel spreadsheet contains all relevant details, selected as Issue Navigator columns, including the test results and the defects (bugs) found.

jira-xray-test-executions.xlsx

Xray test runs

This example, generated from the issue-navigator-with-xray-test-runs.xlsx template, goes into the lowest level details of the individual test runs: version, environment, tester, duration, result, comment, defects, evidences for the whole test and for the individual test steps.

jira-xray-tests-with-test-runs.xlsx

Xray test report

Create reports from Xray tests using the xray-test-report.xlsx template! It calculates the test count and visualizes the test distribution per test repository path, priority, test set, test plan and pre-condition. Or, create your own Xray report by copying and customizing this Excel template.

jira-xray-test-report.xlsx

Xray test run report

The xray-test-run-report.xlsx template gives an easy-to-read overview on test executions and on the individual test runs in those. In its default configuration, it gives pivot tables and charts for test results and defects per test execution, version, environment and the tester person. Like any other template, it can be easily customized to your needs.

jira-xray-test-run-report.xlsx

Learn more about the Xray integration

See the Xray page for a tutorial video and configuration guide.

Structure exports testing requirements management reporting

Structure helps project portfolio managers visualize, track and manage projects with an adaptable, user-defined, spreadsheet-like issue hierarchy. Unlike the two-level hierarchy available in Jira out of the box (issues and sub-tasks), Structure can manage hierarchies with arbitrary depth (trees containing issue nodes). Better Excel Exporter can export structures with the user-selected fields to custom Excel spreadsheets. It is also possible to easily implement structures in any custom Excel template using some concept of "hierarchical issues".

Requirements specification

Structure is a great tool to manage technical requirements for any engineering project, while Better Excel Exporter is great to share those with external parties for reviewing, auditing and analyzing purposes. This example features hierarchical requirements identified by a sequential index (e.g. 1.2.1), collapsible/expandable hierarchy levels, folders for grouping, memos for additional text fragments, plus dependencies and other types of requirement links for the traceability of the items.

jira-structure-requirements-specification.xlsx

Portfolio report (program report)

This multi-level activity list gives a centralized overview to the status of the whole project portfolio. It breaks down agile programs to initiatives, to epics, to stories, to tasks and even to sub-tasks. Better Excel Exporter automatically uses the columns you configured for the Structure view, therefore you can add, remove and re-order columns to the final report effortlessly.

jira-structure-portfolio-report.xlsx

Dynamic task list

Structure's automation features are fully supported by Better Excel Exporter! The dynamic structure exported to this Excel file is an issue set, automatically grouped by sprint (1st level), grouped by assignee (2nd level), and sorted by story points. Note that after the so-called generator items are automatically executed, the resulted issues will be exported.

jira-structure-iterations-overview.xlsx

Learn more about the Structure integration

See the Structure page for a tutorial video and configuration guide.

Insight reports reporting business intelligence asset management

Insight is the leading asset management app for Jira, that allows implementing CMDB, CRM, HR, ITSM or ITIL functionality on the Jira platform. Better Excel Exporter 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 page for a tutorial video and configuration guide.

Git Integration reports version control system git

Git Integration is the most advanced Jira app to integrate the Git version control system with the Jira platform. It supports all major Git servers, including Git itself, GitHub, GitLab, BitBucket, Microsoft Azure DevOps Repos, AWS CodeCommit and Gerrit. Better Excel Exporter can export the Git commits (all details!) associated with the Jira issues, and all Git Integration specific custom fields to Excel. It also offers a report template to create custom development-focused reports from Jira and Git information.

Issues with selected fields and Git commits

Using the issue-navigator-with-git-commits.xlsx template, you can export your issues using the Issue Navigator columns plus additional columns that contain the Git commits linked to the issues. Git commits are exported with these details in the right: repository, branch, commit ID, author, creation time, commit message, commit notes, and changed files.

jira-issues-selected-fields-with-git-commits.xlsx

Development task list with Git branches

This status report document lists the state of all the issues in a Scrum sprint. Using the two Git Integration custom fields, it also shows whether an issue has Git commits associated with it (gitCommitsReferenced column) and which Git branches were affected if any (gitBranch column).

jira-development-task-list-with-git-branches.xlsx

Git development metrics report

The git-report.xslx template allows reporting on the Git commits linked to your Jira issues, in order to measure every step of your development process. This sample has the following reports: commit count per issue, code changes (lines added and deleted) per issue, commit count per author, commit activity per repository (timeline per year and week) and author activity (timeline per year and week). Feel free to customize these or add your own!

jira-git-development-metrics-report.xlsx

Learn more about the Git Integration integration

See the Git Integration page for a tutorial video and configuration guide.

Elements Connect (nFeed) reports reporting data integration business intelligence

The nFeed app integrates external data sources (SQL databases, LDAP, Active Directory, REST APIs, Salesforce, CSV files, etc.) to Jira. Better Excel Exporter 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 page for a tutorial video and configuration guide.

Jira Misc Custom Fields (JMCF) exports scripted fields reporting calculated fields

Jira Misc Custom Fields (JMCF) is an extremely popular Jira app which offers calculated (scripted) custom fields to display information based on computed values. Those result in more useful issue screens, better search, better filtering, more powerful reports and dashboards. Better Excel Exporter exports all the calculated (scripted) fields to Excel for reporting, sharing, ETL (extract, transform, load) purposes.

Issues with JMCF custom fields

This Excel export shows custom field samples of various types, calculated by the Jira Misc Custom Fields app. For example, the "Work Started by" column contains the user who transitioned the issue to the "Under development" status the first time, while "Time in Under Development" contains the time spent in that status, and so on.

jira-misc-custom-fields-export.xlsx

Stories with the most defects report

In this example, a JMCF-powered custom field is used to count the bug-type issues linked to the implementation sub-tasks of each user story, and store that number in the story itself. It is an indirect counter to find the stories with the most implementation defects. Another JMCF custom field stores the story owner (the user who transitioned the story to the "Accepted" status) who appears color coded to the chart.

jira-misc-custom-fields-bugs-per-story-report.xlsx

Low-effort high-impact stories report

This report uses Jira Misc Custom Fields to calculate the total vote count and the total time estimate of the tasks linked to (high priority) user stories, plus the ratio of those two. The bubble chart clearly tells which stories would create the highest value in the shortest time, i.e. which stories should be your top priorities.

jira-misc-custom-fields-low-effort-stories-report.xlsx

Learn more about the Jira Misc Custom Fields integration

See the Jira Misc Custom Fields page for a tutorial video and configuration guide.

Profields exports reporting project custom fields project management

Profields is the project administration app for Jira that enables adding custom fields to projects, such as due dates, budgets and supervisors. It centralizes information that is project-dependent, not issue-dependent, which Better Excel Exporter can export both in the context of issues and in the context of projects. Ultimately, Excel reporting on the Profields data gives project-, program- and portfolio managers more insight to manage, monitor and search across Jira projects.

Issues with Profields custom fields

This export contains issues from multiple projects, with the Profields-managed data of their encompassing projects (column E-L). Note that the Profields values are exported with the precise data types (numbers, dates, etc.).

jira-profields-issue-export.xlsx

Projects with Profields custom fields

Not only issues, but also projects can be exported to Excel (using this technique). If you have a large number of projects, it offers an easy way to search, share and transfer project information between stakeholders or IT systems.

jira-profields-project-export.xlsx

Profields project report

You can also create powerful cross-project, program- and portfolio reports from Profields data. This example contains pivot charts to visualize the project status distribution among projects, the project costs, and the relationship between those (cost by status).

jira-profields-report.xlsx

Learn more about the Profields integration

See the Profields page for a tutorial video and configuration guide.

Time to SLA exports SLA reporting business intelligence

The Time to SLA app is a popular choice to implement Service Level Agreements (SLAs) on Jira issues. It helps to set up, track and measure SLAs based on issue events (status change, resolution, reopen, etc.). Better Excel Exporter is tightly integrated with Time to SLA, allowing you to export all Time to SLA custom fields to Excel in customizable format. Using the Excel features on Time to SLA data, you can easily create powerful SLA reports.

Issues with Time to SLA fields

This basic Excel export (created using the default issue-navigator.xlsx template) contains one column of each Time to SLA custom field type. The idea is to demonstrate the default SLA export format that you can customize to your needs.

jira-time-to-sla-export.xlsx

Learn more about the Time to SLA integration

See the Time to SLA page for a tutorial video and configuration guide.

Color Custom Fields exports visualization risk management project management

Using color-type custom fields to manage issue attributes, that can be intuitively color-coded, will make your information intuitive, visual and easy-to-understand. A good example of this is modeling Impact and Likelihood with a red/yellow/green scale for a special "Risk" issue type in a Risk Management use case. Although color-type custom fields are not available in core Jira, the free Color Custom Fields app can add those as extension and Better Excel Exporter can export those to Excel spreadsheets.

Issue list with Color Custom Fields

This Excel file is an issue list exported from a JQL search result, with all the risks in a given Jira project. Note that the export reminds to a heat-map kind of visualization, which makes communicating the risk factors with the project stakeholders quick and easy.

jira-color-custom-fields-export.xlsx

Learn more about the Color Custom Fields integration

See the Color Custom Fields page for a tutorial video and configuration guide.

Visual Basic enhanced dynamic reports reporting

Exported XLSX files do 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 app 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.

jira-vba-enabled-issue-export.xlsm

Other exports data integration data analysis archiving

Better Excel Exporter 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 projects

The project-export.xlsx template exports Jira projects to Excel, including their keys, names and other details, issue count, components, issue types, versions and archiving information. This export enables reporting on projects, which is completely missing from Jira core functionality.

jira-project-export.xlsx

Jira user accounts

The user-export.xlsx template exports Jira 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

Complex project status report

This custom report template was created by a Better Excel Exporter power user (the original data has been removed for privacy reasons). The report features a customized issue list (with color coding), a Gantt chart-like time planner (using Excel cells!), plus a pivot table and -chart.

jira-project-status-report.xlsx