Team performance widget
Shows the amount of work a team completes over a specific period. This widget helps you monitor workload and forecast it for the coming weeks or months.
You can calculate the amount of work:
- based on the value of a numeric field, such as Story Points;
- based on the number of completed issues;
- based on the time issues spent in selected statuses.
For more information, see Calculation parameters.
Simple chart
The simple chart shows only the actual amount of completed work.
In the screenshot, the amount of work is calculated based on the Time spent parameter, and each column represents a sprint.
Example chart
Chart with sprint plan
You can add the targets the team is aiming for in the current sprint and compare them with the actual result. The chart will show:
- The Plan column — the Story Points or number of issues planned for this sprint. To calculate the plan correctly, add all issues to the sprint before the end of the first day of the sprint.
- The Actual column — the amount of work completed in this sprint.
- The Plan completion percentage line — shows what percentage of the plan the team completes from sprint to sprint.
In the screenshot, the amount of work is calculated based on the Original Story Points parameter, and each column represents a sprint.
Example chart
Adding a plan to the widget
-
Start creating a new widget or edit an existing one: at the top of the widget, click → Edit.
-
For the Time intervals parameter, select Sprint.
-
Select the board where you plan the sprint.
-
Enable the Plan option.
Widget actions
To open the issue list, click a column, then click the number of issues in the drop-down list.
To enlarge a chart area, select it with your mouse.
To return to the original scale, click Reset zoom on the right.
Widget settings
Example settings
Chart parameters
-
Data source — the issue search conditions for the widget. You can specify them in different formats:
- Filter — here you can select a quick filter, such as "Reported by me", or your saved filter. How to save an issue filter
- Query language — here you can enter a condition in query format. Choose this if you need to insert a function or combine several conditions with the "AND" and "OR" operators. How to set a condition using the query language
- Parameters — here you can set up a condition using buttons. How to add search conditions
-
Period — the time span for the entire chart. To make the start date shift every day, select a dynamic range, such as "Last year".
Data source — the issue search conditions for the widget. You can specify them in different formats:
-
Time intervals — the time span for each column, such as a week or a sprint.
-
Final statuses — which statuses you use for completed issues.
Calculation parameters
Each column will show the sum of the values of a specific issue parameter. Choose this if you measure the amount of work by a numeric parameter, such as Story Points or Time spent.
Next, choose how to calculate the value for each issue:
- By last value — the sum will include the parameter value at the time the issue was completed.
- By decrease — the sum will include the number by which the parameter value decreased over the Time interval within the period. Choose this if you estimate the amount of work in advance and then track how much work remains.
Add the latest value before closing the issue, or it won't be included on the chart. - By increase — the sum will include the number by which the parameter value increased over the Time interval within the period. Choose this if your team usually works on issues over several periods.
Add the latest value before closing the issue, or it won't be included on the chart.
The columns will show the number of issues the team completed over the Time interval within the period.
The columns will show the time issues spent in a specific status. The total is rounded to the nearest whole time unit. Choose this if your team closely tracks issue statuses.
You can also select a working schedule — in that case, only working hours will be counted when calculating the metric.
For example, you selected a nine-hour work schedule from 9:00 to 18:00. In this case, 12 hours will be rounded down and appear on the chart as "1 day".
A sprint is a short work cycle in Agile, usually lasting 1–4 weeks. In Tracker, sprints are used on boards with backlogs and sprints.
A status is an issue parameter that shows the current stage of the issue. For example , , .
A story point is an estimate of the relative complexity of issues. Each team defines its own way of estimating issue effort. You need to specify the estimate on the issue page.