You can configure the chart according to your processes and needs in the “Main” tab in the settings of all related charts:
Use one of the saved filters
If you have the filter you use on your board, you can select it from the menu. Type the first letters to start the search:
Note: To select the filter, you need to have permissions. Contact your Jira admin for details.
Filter issues from Scrum and Kanban boards at the same time
Given:
You have two teams working in two different methodologies: Scrum and Kanban
You want to track their progress as one team of teams
In that case, you can create your own Custom JQL filter:
Note: Some functions can lead to fast data expiring.
More details: https://brokenbuild.atlassian.net/wiki/pages/createpage.action?spaceKey=BB&title=Using%20JQL%20functions%20with%20enabled%20caching
Filter issues from a particular Release/Epic across all boards
Given:
You have more than one team working on some Release (or Epic)
You want to track their progress as one team of teams
In that case, you can create your own Custom JQL filter:
Note: The chart uses your Jira instance filter engine with all supported functions. If you install some filter-extending plugins, it will affect the chart’s JQL filter functionality.
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 (e.g., Ready for Release, Deployed, etc.)
Several Done status as a group
Any other status as a result of a sub-process
Note: By default, the chart calculates as completed all issues that have any status from the Done category.