Versions Compared

Key

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

...

Setting

Description

Gadget title

Choose what to display in the title bar of the gadget.

Data source

Select the type of Data source used by the gadget:

  • ASaved filterthat contains the Jira issues in your release (the scope of your project release). Make sure that the specified filter is shared if you want other people to visualize the dashboard.

  • A JQL query that returns the issues you want to be processed by the gadget.

Release start date

The start date of your release.

Release end date

The end date of your release

Time interval

Represents the time interval of the release.

You choose from multiple options:

Custom dates - choose this option if you want to manually enter the Start date and End date of the release.

Dates of a project release - Choose this option if you want the gadget to use the start and end dates of an existing project release (added on the Releases page of a Jira project). Make sure the selected release has a Start date and End date set. Any subsequent changes to the release dates made on the project's Releases page will be automatically reflected in the gadget, without the need to reconfigure it.

Be aware that you can also check the Continue to display data after release end date option in the More Settings tab if you want the chart to still display data even if the end date has passed.

Intervals of

Indicates the time interval for calculating the chart data. If you do Agile development, this should be set according to the length of your sprints or iterations.

Calculate by

Specify on which criteria the calculation to be performed. You can choose between:

  • Story Points - the default value; use this option if the issues are estimated in Story Points. If the issues are from team-managed projects (aka next-gen projects), select Story Point Estimate instead.

  • Original Time Estimate - use this if you use time estimates; calculation will be done in hours. The Scope will be calculated as the sum of the Original Estimate field of all the issues from the filter, and each time an issue is marked as done, the Burned and Remaining lines will increase/decrease with the amount of hours that is set at Original Estimate for that issue. This option does not consider the time spent (work logged).

  • Time Remaining & Time Spent - use this option if you use time estimates and your team logs the worked time on a daily basis; calculation will be done in hours. The Scope will be calculated as the sum of the Time Spent and Time Remaining of all the issues from the filter. Burned is calculated as the sum of Time Spent of all the issues from the filter plus the sum of Time Remaining of all the issues from the filter that are done. Remaining is calculated as Scope minus Burned. This option does not consider the Original Estimate field.

  • Issue Count - use this if you want the calculation to be done by the number of issues.

  • Other numerical custom fields defined in your Jira instance - pickup the numerical custom field that you use to track or estimate the issues.

...

Setting

Description

End date forecast based on

Specify how the end date forecast is calculated.

The average velocity of all the completed intervals - by choosing this option the end date forecast will be calculated based on the average velocity (average amount of work completed) of all the completed time intervals from the chart.

The average velocity of the last x intervals - by choosing this option the scope forecast will be calculated based on the average velocity (average amount of work completed) of the most recent x completed time intervals from the chart.

A fixed velocity of … - by choosing this option the scope forecast will be calculated based on a fixed velocity, entered manually.

These settings affect all the forecast series, except Forecast Scope.

Consider the scope forecast when making the end date forecast

By checking this option, the calculation of the end date forecast will also take into account the scope forecast, not just the velocity.

This setting affects all the forecast series, except Forecast Scope

.

Scope forecast based on

Specify how the scope forecast is calculated.

The average scope changes of all the completed intervals - by choosing this option the scope forecast will be calculated based on the average scope change ratio of all the completed time intervals from the chart.

The average scope changes of the last x intervals - by choosing this option the scope forecast will be calculated based on the average scope change ratio of the most recent x completed time intervals from the chart.

A fixed scope change ratio of … - by choosing this option the scope forecast will be calculated based on a fixed change scope ratio, entered manually.

These settings affect the Forecast Scope series, as well as the other forecast series if the Consider the scope forecast when making the end date forecast is checked.

...