Versions Compared

Old Version 6

changes.mady.by.user Yuri

Saved on

compared with

New Version Current

changes.mady.by.user Yuri

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Reports for Versions

Version Burnup

Info

Available for Fix Versions only. Coming soon for Epics and Sprints. Not available for JQL Versions.

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. 

...

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. 

Note

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

...

The resulted document structure is:

Code Block
"Date","Total","Completed"
"2019/10/28","87","16"

Version Trends

Info

Available for Fix Versions only. Coming soon for Epics and Sprints. Not available for JQL Versions.

This report helps to outline “scope change” and “done items“velocity trends of the version. 

...

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.

...

Info

Few popular Use Cases:

  • Bugs trend report: issueType=Bug (Units: Issue count)

  • Version velocity: issueType in standardIssueTypes() (Units: Any)

  • Business value delivered trend: issueType in (Task, Story, Epic) (Units: Issue count or Story Points)

  • Performance per person: assignee was <user_name> (Units: Any)

...

The report has the following content:

  1. Period of the data aggregation. The 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 Packages

Package Burnup

Package burnup chart is similar version burnup though provides some additional sophisticated features for Release Managers to use. It consists of two main parts:

  1. Cumulative package progress. The chart shows the cumulative scope and progress for all the versions in the package on a daily base

  2. Individual versions progress. Separate charts for each version in the package. 

...

Report logic is the same comparing to versions burnup.

...

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

  1. Cumulative trends for all version in the package. 

  2. Separate trends for individual version in the package. 

...

Package Status Report

Package status report helps users to understand the overall status of the package and all its included versions.

...

Other Reports

Scope Change Report

Info

Available for fixVersions only, not the Virtual versions.

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

...