All the reports are available in the Reports section of Release Board:

  • Version Burnup report
  • Release Burnup report
  • Release Status report
  • Scope Change report
  • Board statistics report

Reports for Versions

Version Burnup Chart


Only applicable for Fix Versions as we can't yet track history for Virtual Versions.

Version burnup report helps you to monitor version scope and development progress over time. It also allows spotting expected or unexpected scope changes and version progress trend. 

Report configuration

User can choose any version in the board using version selector:

Available units are:

  • Issue count
  • Original time estimate
  • Story points (Jira software only)

User can adjust report output via custom JQL queries:

Few popular Use Cases:

New features and technical improvements burnupissueType in (Epic, Story, Task) 
Exclude sub-tasksissueType in standardIssueTypes()
Burnup for assigneeassignee was <user_name>

Also, user can choose from additional drawing options:

  1. Draw version from the start date. If the option is enabled, the report is drawn from the version start date. Otherwise, from the date when the first item was added into the version. 

    The option is not available if version start date is empty.

Report content

  1. Total scope of the version calculated on a daily base in selected units
  2. Done scope of the version
  3. Guideline. Shows ideal burnup rate in order to complete version in time. 

    Guideline is only available if Start and Release dates are specified.

  4. Version and release forecast. Draw optimistic, realistic and pessimistic guidelines based on the projected release date. Please read more details on how the projected release date calculated in FAQ

    The forecast guideline will be drowned if the projected release date is calculated.

  5. Start date. Indicates version start date
  6. Release date. Indicates version release date
  7. Version status change. Indicates when the version was moved from one column to another one. The details are available on mouse-over. 

Export to CSV

Total scope and amount of done items could be exported in CSV format using button.

The resulted document structure is:


Version Trends Report


Only applicable for Fix Versions as we can't yet track history for Virtual Versions.

This report helps to outline scope change and velocity trends of the version. 

Report configuration

Following configuration parameters are available:

  1. Version selector. Choose a version for which the report will be built.
  2. Data aggregation interval. The user can choose an interval for which the data will be aggregated in the report. Available options:
    1. Day
    2. Week
    3. Month  
  3. Unit. Supported units are:
    1. Issue count
    2. Story points
    3. Original time estimate
  4. JQL. The report content could be adjusted via custom JQL function.
  5. Done items switcher. Turn on/off done items trend (meaning: version velocity)
  6. Scope change switcher. Turn on/off scope change trend. 
  7. Draw from start date. If the option is enabled, the report is drawn from the version start date. Otherwise, from the date when the first item was added into the version. 

    The option is not available if version start date is empty.

Few popular Use Cases:


Bugs trend report

issueType=BugIssue count
Version velocityissueType in standardIssueTypes()Any
Business value trendissueType in (Task, Story, Epic)Issue count or Story Points
Performance per personassignee was <user_name>Any

Report content

The report has the following content:

  1. Period of the data aggregation. Te values are calculated by the formula: <# of items in period>= <# of items at the end of the period> - <# of items at the start of the period> +1 day 
  2. Scope change trend line.
  3. Velocity trend line.
  4. Scope change and velocity for the current period are outlined with a dotted line.

Reports for Releases

Release Trends Report


Will only take Fix Versions of specified release in account. For Virtual Versions we can't yet track history.

Release trends report is similar version trends report. It consists of two main parts:

  1. Cumulative trends for all version in the release. 
  2. Separate trends for each version in the release. 

Release Burnup Chart

Release burnup chart is similar version burnup. It consists of two main parts:

  1. Cumulative scope. The chart shows the cumulative scope and progress for all the versions in the release on a daily base
  2. Separate charts for each version on the release. 

Report logic is similar to versions burnup.

Release Status Report

Release status report helps users to understand the status of the release and all its versions.

The following information about the release and its versions is available:

  • Status
  • Issues progress
  • Start date
  • Release date
  • Projected release date

User can select any release available in the Release Board using the Releases selector:

Release Milestones Reports

Release milestone report gives you an aggregated view on all milestones of cross-project release and its associated versions. 

To open the report choose "Milestones" in release section of "Switch report" drop down.

Choose one or several of your cross-project releases to generate the report.

How to read track bar?

  • Achieved states for milestones achieved at a date <= planned date
  • Achieved with delay states for milestones ticked as achieved at a date > planned date
  • On track means not yet achieved, but the planned date is in future (or empty)
  • Delayed means not yet achieved with planned date in the past

Adjustments and configuration

You can adjust the output by configuring some predefined filters:

  • Delayed will shortlist only delayed milestones, not delayed or ALL
  • Achieved will shortlist only achieved milestones, not achieved or ALL
  • By clicking on "Export to CSV" you can download the output

If you want to go into further details and see version specific milestones toggle "Show detailsat the bottom of the report.

Other Reports

Scope Change Report


Only applicable for Fix Versions as we can't yet track history for Virtual Versions.

Scope change report helps users to identify the issues that caused affect on the scope of a version or release.

The report has two sections:

  • Added issues - issues which were added to the target version or release during a specified period 
  • Removed issues - issues which were removed from the target version or release during a specified period

Report parameters include:

  • Target version or release
  • Predefined date periods with the option to specify custom start and end dates
  • Filter by issue types

The following issues details are displayed:

  • Issue type, key, summary
  • Status
  • Priority
  • Currently assigned versions from "fixVersions" field
  • Story points
  • Original, remaining and logged work (hours)

The total number of issues in each section is displayed together with the Sum of Story Points and Time Tracking fields.

Board Statistics 

The report shows the number of transitions into each column for version and release.

Transition statistics for release will be calculated since version 3.3.0 of the Release management app will be installed.

Reports configuration

User is able to define the following configuration parameters:

  • Period. Defines a period for which the statistic will be generated.

Report content

  1. Statistics for all versions in the board
  2. Statistics for all releases in the board
  3. Number of versions or releases which were moved to a particular status during the selected period
  4. Transition detail button. It opens a pop-up with all transitions to the selected status.

    Transition details button is only available if 

  5. Export to CSV

More "Reports"?

In the "More reports" section we compiled the list of reports that we want your feedback and votes for.

Click the "Vote" button to let us know which on you find particularly useful.

Release & Version BurndownTrack the total work remaining and project real release date. This helps you to manage release or version progress and respond accordingly.
Release Velocity ChartControl your release velocity over time through each particular version velocity monitoring. Identify velocity degradation and potential delays upfront.

Suggest your report

We are open to your feedback! If you have an idea or need any other report, please let us know using the simple feedback form:

  • Report name - required field
  • Report description - required field
  • Your email - this is optional if you want to let us know to contact you about your suggestion.