All the reports are available in the Reports section of Release Board. Here’s the list what we support at the moment:
Version burnup report helps you track version scope changes and development progress over time. It also allows highlighting expected or unexpected scope changes and version progress trend towards expected release date.
User can choose any version in the board using version selector:
Available units are:
Issue Count
Story Points
Original time estimate
User can adjust report output via custom JQL queries:
Few popular Use Cases: New features and technical improvements burnup: issueType in (Epic, Story, Task) |
Also, user can choose from additional drawing options:
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. |
1. Total scope of the version is 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. Start date. Indicates version start date
5. Release date. Indicates version release date
Total scope and amount of “Done” items could be exported in CSV format in case you want to build a more sophisticated view with XLS or Google Spreadsheets.
The resulted document structure is:
|
Coming soon …
Package burnup chart is similar version burnup though provides some additional sophisticated features for Release Managers to use. It consists of two main parts:
Cumulative package progress. The chart shows the cumulative scope and progress for all the versions in the package on a daily base
Individual versions progress. Separate charts for each version in the package.
Report logic is the same comparing to versions burnup.
If you click on “Draw from Start Date“ both cumulative and individual versions burn ups will be adjusted and depicted from package start date. Thus you can see what specific versions contributed to scope / progress change on daily basis. |
Coming soon …
Package status report helps users to understand the overall status of the package and all its included versions.
The following information about the package and its versions is available:
Status
Issues progress
Start date
Release date
User can select any package available in the Release Board using the Package selector:
Scope change report helps users to identify the issues that caused affect on the scope of a version or package.
The report has two sections:
Added issues - issues which were added to the target version or package during a specified period
Removed issues - issues which were removed from the target version or package during a specified period
Report parameters include:
Target version or package
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.
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.