Overview

Sometimes we mixed up releases and versions, but think that you release a version of your project with specific features. In Jira Software, each release is called a version. So, it’s a point in time of your project where you plan to deliver value to your customers. Versions have different status (unreleased, archived or released) depending on the stage of your software cycle.

This gadget displays the last three unreleased versions of the selected project. The idea is to give a quick hint of our main goal: Deliver, deliver, deliver! If there are not three, then, the last released versions, and if there are not enough to fill those three versions, then the last archived versions. It shows: The version name, the version status (unreleased, archived or released), the number of issues in each status and the start and release dates (if any).

Configuration

Name your gadget meaningfully, so everyone knows at a glance when to use it. Fill out the rest of the fields as applicable, namely:

  • The datasource, where Current indicates the Jira cloud instance where the app is installed.

  • The project of the releases we want to display.

  • The estimation statistic, choose how the work in the releases is indicated. Remember, issues without an estimation are not reflected in the calculation.

    • Story points (classic projects). The work done in the release will be measured by the story points estimations the team did in the backlog

    • Story points estimate (next-gen projects). The work done in the release will be measured by the story points estimations the team did in the backlog.

    • Original time estimate. The work done in the release will be measured by the time estimations the team did in the backlog i.e., duration of the issues in hours or days in the Original Estimate field.

    • Issue count. The work done in the release will be measured by the number of issues completed. And they won’t need to enter estimates in the backlog. Thus the sum of the issues in a status divided by how many issues are in total in the sprint e.g., 50 issues in the sprint, 25 are in status “Done” so 50% is indicated

Learn about Configure estimation and tracking in classic boards

  • Finally, indicate if you want to use the current settings for all the compatible gadgets in the dashboard. This option eases the pain of configuring one by one the rest of the gadgets with the same default configuration

Integrations

We are working on our growing catalog of Gadgets: KPIs and Metrics, but drop us a line in case you want us to expedite a specific one, visit our Help Center.

Dashboards

This gadget appears in the following dashboard: Scrum Software Team template

See also