Using Scrum boards
- Olexiy Artemenko
You can configure the chart according to your processes and needs in the “Main” tab in the settings of all related charts:
One team per one Scrum board
In that case, you can select all Scrum boards you want to track across. If you don’t see the needed Scrum board in the list, start typing the name, and the search will find it:
Note: The app is using your Jira instance search engine, so if you select too many boards, the calculation can take a long time before we cache it. “Too many” is an empirical value and depends on your work log amount.
Several teams using one Scrum board
Given:
You use the Sprint name to navigate your teams through the Scrum board.
You want only some of them to be visualized on the chart.
In that case, you can select one Scrum board multiple times and define the Sprint name filter:
Company-managed vs. team-managed projects (custom estimation field)
Given:
One team is using a company-managed project with a “Story points” default estimation field.
Another team is using a team-managed project with a “Story point estimate” default estimation field.
In that case, the general estimation field will be set, inheriting the default value of the first added board so that you can customize other boards' settings:
The color of the icon button will show you what board settings are customized:
Integrated "Time Spent & Remaining Time" Estimation Field
By merging the two types of data — time spent and time remaining — your teams can continue using familiar tools while applying agile principles to track their performance. This blended approach can offer you a more nuanced view of team workflow close to Story Points, ensuring a smoother transition and more accurate forecasting.
You can select the "Time Spent & Remaining Time" field from the dropdown alongside other fields.
By default, the charts focus on the team’s productivity by counting Time Spent and Remaining Time for completed issues. In contrast, you can switch on the toggle to track the team’s efficiency and consider only the Time Spent.
To get more details about configuration and calculation, please read this article.
Custom Done statuses
In case your workflow goes beyond the standard delivery process and you want to track the following:
Specific Done statuses for one or different boards (e.g., Ready for Release, Deployed, etc.)
More than one Done status for the one board
Any other status as a result of a sub-process
You can select more than one status for the particular board:
The color of the icon button will show you what board settings are customized:
Note: By default, the chart calculates as completed all issues that have any status from the last column of the board workflow, getting this from the board settings.
Applied to