Versions Compared

Key

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

...

To generate report you need to choose one of the items on your Plan as well as specify what numeric property you would like to use to generate summary and aggregation range of the report.

...

...

Version selector. Choose a version for which the report will be built.

...

We support the following aggregation date ranges:

  • Day

  • Week

  • Month  

...

Unit. Supported units are:

  1. Issue count

  2. Story points

  3. Original time estimate

...

JQL. The report content could be adjusted via custom JQL function.

...

Done items switcher. Turn on/off done items trend (meaning: version velocity)

...

Scope change switcher. Turn on/off scope change trend. 

...

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.

...

User can adjust report output via custom JQL queries:

...

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:

  • 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 

  • Scope change trend line (can be turned ON|OFF).

  • Velocity trend line (can be turned ON|OFF).

  • Scope change and velocity for the current period are outlined with a dotted line.

...

Scope Change Report

Info

Available for fixVersions only, not the Virtual versionsReleases (Versions) and not available for Epics, Sprints yet. Impossible to do for Custom JQL Releases.

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

The report has two sections:

  • Added issues - issues which were added to the target version or package plan item during a specified period 

  • Removed issues - issues which were removed from the target version or package plan item during a specified period

Report parameters include:

  • Target version or packageplan item

  • Predefined date periods with the option to specify custom start and end dates

  • Filter by issue types

...

  • Issue type, key, summary

  • Status

  • Priority

  • Currently assigned versions from "fixVersions" field

  • Story pointsEstimation (configurable)

  • Original, remaining and logged work (hours)

The total number of issues in each section is displayed together with the Sum of Story Points Estimation (configurable) 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

...

via our service desc portal.