Agile Charts & Gadgets: Reports, Graphs, KPIs on Dashboard

This release includes the following fixes for Cycle Time Charts:

• Story Point breakdowns are clearer, with values displayed directly instead of only on hover.
• Mean values in the breakdown tables are correctly calculated per row.
• Estimation field filters work as expected and no longer result in empty charts.

Release notes

Release notes

This release includes:

• Forecast delivery dates based on the Epic estimates
• JQL Epic filter
• Merge of dozens of statuses with the same names into one option in the custom Done configuration
• Export to CSV in Cycle Time charts
• Rollover calculation aligned with the sprint filter
• Fixed Burndown and Burnup charts freezing the browser during chart loads
• Fixed the time zone in the work schedule affecting all calculations

Release notes

This release includes next bug fixes:

• Using “activatedDate” instead of startDate(planned) of the sprint for calculations
• Fixes chart calculation when using a specific Timezone in global settings

Release notes

This release includes:

• Reports visibility fix

Release notes

This release includes:

• Fix project search

Release notes

This release includes:

• Fix calculations for multiple boards

Release notes

This release includes:

• Fix an issue with reports migration

Release notes

This release includes:

• Improve error logging

Release notes

This release includes:

• Report and board set migration improvements

Release notes

This release includes:

• Burnup Burndown Charts:
  • Alternative throughput date for forecasting before the project gets its own velocity history
  • Health Metrics
  • Metric visibility configuration
  • Hidden features related to the Remaining work are now more discoverable
  • Breakdown the completed work during the whole date range as one cohort
  • New templates for Velocity percentile and Monte Carlo scenarios
• Cycle Time Charts:
  • The time in status chart and the transition count table in the right bar of the issue layout

Release notes

This release includes several minor bug fixes:

• Fixed an app crash in Confluence Data Center when opening the issues filter section in the chart configuration.
• Fixed an app crash that occurred when time tracking was disabled on the instance.

This release includes several major updates that allow you to track progress towards objectives and forecast delivery dates better:

• Velocity, Cycle Time, and Burnup/Burndown charts on the project page
• Burnup/Burndown improvements:
  • Improved UX for forecast scenarios
  • Velocity percentile scenario
  • Monte Carlo simulation scenario
  • Burndown chart now reflects the Remaining work changes
  • Daily Burndown for any data source
  • Velocity/resource allocation coefficient

and many more slight refinements…

Release notes

Release notes

This release includes several enhancements to the Issue hierarchies (formerly Initiatives) data source:

• Only project-related statuses are available to select when using the Jira project as a data source
• 3 levels of hierarchy depth and a clear definition of what will be shown on the chart, when using the Issues hierarchy data source
• JQL filter to select multiple items in the Issues hierarchy data source
• Ability to select completed work items in the Issues hierarchy data source
• Fixed fixVersion id value provided as array ['123'] instead of 123

Release notes

This release includes several enhancements to the Issue hierarchies (formerly Initiatives) data source:

• Only project-related statuses are available to select when using the Jira project as a data source
• 3 levels of hierarchy depth and a clear definition of what will be shown on the chart, when using the Issues hierarchy data source
• JQL filter to select multiple items in the Issues hierarchy data source
• Ability to select completed work items in the Issues hierarchy data source
• Fixed fixVersion id value provided as array ['123'] instead of 123

Release notes

Release notes

This release includes the following fixes and improvements:

• Fixed loading Agile Reports macro in Confluence 9.x+
• Fixed date picker cropped in a Confluence macro configuration
• Cycle Time Chart: fixed incorrect loading of saved filters in the data source dropdown
• Cycle Time Chart: speed up work items search

Release notes

Release notes

This release includes:

• Fixed the wrong Time in Status calculation
• Fixed the absence of the reset cache button in cycle time reports & gadgets
• Replaced the deprecated search issue endpoint with a new one

Release notes

This release includes:

• Fixed Cycle Time chart crashing for specific settings configuration
• Fixed Cycle Time chart breakdown data when one interval is available on the chart

Release notes

This release includes:

• Fixed Cycle Time gadget settings not saving
• Fixed Sprint Burndown chart not loading on specific instances

Release notes

This release includes:

• Cycle time chart: Fixed an issue with duplicated issue types in the issues filter.
• Fixed chart crashes with time-tracking estimation when intervals have deleted issues in the cache.
• Fixed issue with reports not opening – Reports were inaccessible in some permissions configurations.

Release notes

This release includes:

• Live Data Link Feature End-of-Life
• Fixed issue where the second macro copied settings instead of retaining its own

Release notes

This release includes:

• Atlassian Team field support (All charts)
  • For those who have adopted Atlassian's new feature to assign work to a specific team, we’ve started supporting the Atlassian Team field in the breakdown.
• Transition Count (Cycle Time charts)
  • To understand where the flaw in the workflow lies, in addition to cycle time and time in status for each issue, it’s crucial to view how many times an issue has transitioned to each status. Now, you can examine the number of status transitions for each issue within the chart's scope and see it broken down by status, allowing you to investigate potential issues.

Release notes

This version contains the following fixes:

• Crash in Burnup Chart for JQL filters selected big amount of epics
• Missing "Date picker" in chart configurations

Release notes

This release includes:

• Cycle Time Charts: Performance improvements
• Cycle Time Charts: Fixed not fetching the data for added columns in the issue list
• Cycle Time Charts: Fixed absence of “Board” as a breakdown option
• Velocity Charts: Fixed error when saving the report with the Custom JQL instead of the board
• Velocity Charts: Fixed not counting an issue as “removed from sprint” when it was completed outside
• All Charts: Temporarily removed the recent reports functionality due to crashes on Jira 10.3.2

Release notes

Fixed an issue in the Cycle Time Report where Jira keyboard shortcuts (e.g., 'a', 'c', 'g') disrupted typing in the JQL Filter field.

Since this version, you can measure cycles and time spent in different statuses for the “idea” issue type and Product Discovery (PD) projects. This is possible even though these are not explicitly listed among all issue types and Jira projects (due to Atlassian internal limitations). To enable this, we support you to use simple workarounds.

On top of that, we continue making the Cycle Time Charts app the most advanced tool for measuring the flow.

This time, we introduce the Time in Status analytics toolset updated with the following features:

• Status groups
• The Ratio view in the Time in Status chart
• The Average per Issue view in the Time in Status chart
• Target lines in Time in Status chart
• Apply button for JQL filter

To get more details, please read the full release notes.

This release contains several UX improvements for Cycle Time charts:

• Chart description tooltip
• Exclude issues from the calculation
• Issue state configuration moved to the toolbar above the chart
• Improved performance
• Added pagination for the issue list
• Clicking on the chart elements opens the issue list
• Fixed issues appearing twice in different periods if the sprint field was updated
• Fixed Cycle Time charts' macro not working in Confluence

Release notes

Release notes

Release notes

This release includes three charts:

• Cycle Time Histogram
• Time in Status
• Cycle Time Trend

Key features:

• 3 Cycle Time Jira Charts: switch between chart types to get a complete picture of your workflows
• Flexible Data Sources: integrate data from boards and filter issues with JQL. Perfect for Epics, Initiatives, or any issue hierarchy
• 2-Level Cycle Time Breakdown: slice and dice your data any way you like, with detailed issue lists for deep dives
• Precise Scheduling: holidays, days off, and breaks in work schedule calculations
• Visual Cues: highlights, thresholds, and targets help you spot when cycle times exceed limits or meet goals
• Advanced Filters: focus on specific entities like bugs or stories. Compare estimation units with actual cycle time
• Accurate Time Tracking: timer tracks precisely where time is spent in a workflow

Release Notes

This release includes three charts:

• Cycle Time Histogram
• Time in Status
• Cycle Time Trend

Key features:

• 3 Cycle Time Jira Charts: switch between chart types to get a complete picture of your workflows
• Flexible Data Sources: integrate data from boards and filter issues with JQL. Perfect for Epics, Initiatives, or any issue hierarchy
• 2-Level Cycle Time Breakdown: slice and dice your data any way you like, with detailed issue lists for deep dives
• Precise Scheduling: holidays, days off, and breaks in work schedule calculations
• Visual Cues: highlights, thresholds, and targets help you spot when cycle times exceed limits or meet goals
• Advanced Filters: focus on specific entities like bugs or stories. Compare estimation units with actual cycle time
• Accurate Time Tracking: timer tracks precisely where time is spent in a workflow

Release Notes

We implemented an improvement for users who encountered a white screen instead of seeing gadgets load. Decreasing the app file size ensures it can now load within the platform’s limited timeframe.

Release notes

We implemented an improvement for users who encountered a white screen instead of seeing gadgets load. Decreasing the app file size ensures it can now load within the platform’s limited timeframe.

Release notes

Now, you can add future sprints to individual charts to manage your team members’ upcoming workload. To do this, enable the future sprints (sprints that have not started but have dates set) in the settings.

Release notes

Now, you can add future sprints to individual charts to manage your team members’ upcoming workload. To do this, enable the future sprints (sprints that have not started but have dates set) in the settings.

Release notes

This update extends compatibility to Jira Data Center versions up to 10.0.1, ensuring the app works seamlessly with Jira Data Center versions 8.20.0 through 10.0.1. By upgrading, users gain the benefit of stable integration across these Jira platforms, allowing for continued support of key features.

We recommend updating to this version to maintain compatibility with the latest Jira Data Center releases.

Release notes

This update extends compatibility to Jira Data Center versions up to 10.0.1, ensuring the app works seamlessly with Jira Data Center versions 8.20.0 through 10.0.1. By upgrading, users gain the benefit of stable integration across these Jira platforms, allowing for continued support of key features.

We recommend updating to this version to maintain compatibility with the latest Jira Data Center releases.

Release notes

Fixed an issue causing the Velocity Chart for Scrum boards to crash when filtering sprints with partial sprint names.

Release notes

Fixed an issue causing the Velocity Chart for Scrum boards to crash when filtering sprints with partial sprint names.

Release notes

Release notes

Release notes

Your favored breakdowns are now available in Burnup and Burndown charts, allowing you to slice and dice the completed work data to gain insights into its distribution among different segments. Moreover, you can segment the remaining work to manage the scope according to your goals.

Release notes

Your favored breakdowns are now available in Burnup and Burndown charts, allowing you to slice and dice the completed work data to gain insights into its distribution among different segments. Moreover, you can segment the remaining work to manage the scope according to your goals.

Release notes

This release includes two significant enhancements:

• Beyond the default issue fields for slicing your delivery data, we’ve now added the flexibility to choose any field that makes sense for you.
• If you have workflow stages considered “almost Done” and prefer not to count issues in that stage as Rollover, you can select those statuses in the chart settings.

Release notes

This release includes two significant enhancements:

• Beyond the default issue fields for slicing your delivery data, we’ve now added the flexibility to choose any field that makes sense for you.
• If you have workflow stages considered “almost Done” and prefer not to count issues in that stage as Rollover, you can select those statuses in the chart settings.

Release notes

We continue to improve the breakdown feature with two enhancements:

We continue to improve the breakdown feature with two enhancements:

As a user of Jira DC with a configured two-level-above-the-epic Issue Hierarchy, you can now use a parent field to link Initiatives with Epics, enabling them to serve as data sources for your Burnup chart for Initiatives.

Release notes

As a user of Jira DC with a configured two-level-above-the-epic Issue Hierarchy, you can now use a parent field to link Initiatives with Epics, enabling them to serve as data sources for your Burnup chart for Initiatives.

Release notes

• Fixed velocity not calculating automatically for the "what-if" scenario when a valid date is selected
• Added missing converter for seconds to hours to the time tracking target lines.

Release notes

• Fixed velocity not calculating automatically for the "what-if" scenario when a valid date is selected
• Added missing converter for seconds to hours to the time tracking target lines.

Release notes

This release includes usability enhancements and provide greater flexibility, along with several bug fixes to ensure a smoother experience:

• Added a setting to the Benchmarking chart to allow users to select multiple metrics and display a target line.
• Added the option to disable active sprint switching in Global Settings.
• Added the ability to refresh a single gadget instead of refreshing all gadgets on the dashboard.
• Added the ability to open issues directly from the issue list while maintaining the context of the report/gadget.
• Fixed the median value displayed for each period/interval on the chart when the "All intervals" option is selected.
• Fixed Burnup/Burndown charts for Scrum not calculating all active sprints if they are parallel on the board.
• Fixed error in Sprint Burndown import of valid settings.
• Fixed the broken JQL filter validation in the Burnup for JQL gadget.
• Fixed the target dates not displayed on the forecast charts.

Release notes

This release includes usability enhancements and provide greater flexibility, along with several bug fixes to ensure a smoother experience:

• Added a setting to the Benchmarking chart to allow users to select multiple metrics and display a target line.
• Added the option to disable active sprint switching in Global Settings.
• Added the ability to refresh a single gadget instead of refreshing all gadgets on the dashboard.
• Added the ability to open issues directly from the issue list while maintaining the context of the report/gadget.
• Fixed the median value displayed for each period/interval on the chart when the "All intervals" option is selected.
• Fixed Burnup/Burndown charts for Scrum not calculating all active sprints if they are parallel on the board.
• Fixed error in Sprint Burndown import of valid settings.
• Fixed the broken JQL filter validation in the Burnup for JQL gadget.
• Fixed the target dates not displayed on the forecast charts.

Release notes

We continue to add more useful settings and capabilities for small teams and scaled enterprises.

This release includes:

• Live Data Link for DC
• Ability to add multiple Initiatives in the Burnup chart
• Show metrics and average lines independently in Velocity charts for Scrum boards
• CSV export / Live Data link in Benchmarking chart for Scrum boards
• Custom Done statuses configuration to Burnup for Epics
• Lazy loading in the Individual Velocity chart when users are grouped by sprints
• Fixed incorrect minutes calculation when the integrated Time Tracking estimation field is selected

Release notes

We continue to add more useful settings and capabilities for small teams and scaled enterprises.

This release includes:

• Live Data Link for DC
• Ability to add multiple Initiatives in the Burnup chart
• Show metrics and average lines independently in Velocity charts for Scrum boards
• CSV export / Live Data link in Benchmarking chart for Scrum boards
• Custom Done statuses configuration to Burnup for Epics
• Lazy loading in the Individual Velocity chart when users are grouped by sprints
• Fixed incorrect minutes calculation when the integrated Time Tracking estimation field is selected

Release notes

The release includes the following bug fixes:

• Fixed not showing future sprints in Velocity charts
• Fixed not limiting active sprints by sprint count
• Fixed problems with settings migration from the Server/DC to Cloud because of gadget key change

Release notes

The release includes the following bug fixes:

• Fixed not showing future sprints in Velocity charts
• Fixed not limiting active sprints by sprint count
• Fixed problems with settings migration from the Server/DC to Cloud because of gadget key change

Release notes

Our focus on the enterprise sector has grown since last year, when we shifted from team-level reporting to cross-team reporting in organisations, as reflected in version 6.0.0 and subsequent versions of the Agile Reports and Gadgets app (ARG). Considering all observations and collected feedback, we have designed and developed numerous new features in ARG. These features open a new chapter in Delivery Analytics for Scaled Agile, titled "Sprint Metrics' Breakdown & Benchmarking."

Release includes:

• Sprint Metrics
  • Rollover
  • Total Scope change
  • Completed work (initial) update
• Breakdown
  • By issue-level data
  • By org-level data
• Benchmarking
  • Velocity charts' new capabilities
  • New Team/Cross-team Benchmarking chart for Scrum boards

Release notes

Our focus on the enterprise sector has grown since last year, when we shifted from team-level reporting to cross-team reporting in organisations, as reflected in version 6.0.0 and subsequent versions of the Agile Reports and Gadgets app (ARG). Considering all observations and collected feedback, we have designed and developed numerous new features in ARG. These features open a new chapter in Delivery Analytics for Scaled Agile, titled "Sprint Metrics' Breakdown & Benchmarking."

Release includes:

• Sprint Metrics
  • Rollover
  • Total Scope change
  • Completed work (initial) update
• Breakdown
  • By issue-level data
  • By org-level data
• Benchmarking
  • Velocity charts' new capabilities
  • New Team/Cross-team Benchmarking chart for Scrum boards

Release notes

Fixed:

• The Velocity chart was displayed without adhering to the basic configuration settings
• The Personal Velocity chart now adheres to any custom "Done" status configurations set by the user

Fixed:

• The Velocity chart was displayed without adhering to the basic configuration settings
• The Personal Velocity chart now adheres to any custom "Done" status configurations set by the user

Release notes

Release notes

• New Burnup chart for Epics
• Highlight the selected Sprint or Interval details in Burnup and Burndown charts

Release notes

• New Burnup chart for Epics
• Highlight the selected Sprint or Interval details in Burnup and Burndown charts

Release notes

• Added Target Dates to Burnup & Burndown charts
• Introduced chart lazy loading
• Add JQL filter input to Forecast tab for Burnup & Burndown charts

Release notes

• Added Target Dates to Burnup & Burndown charts
• Introduced chart lazy loading
• Add JQL filter input to Forecast tab for Burnup & Burndown charts

Release notes

The process of selecting numerous boards as data sources every time new charts are created becomes cumbersome. To tackle this issue, we introduced the 'Board set' feature. This feature simplifies the aggregation of Sprint and Kanban metrics for large units by enabling the selection of multiple boards as a single data source with just one click, thereby streamlining the chart creation process.

Release notes

The process of selecting numerous boards as data sources every time new charts are created becomes cumbersome. To tackle this issue, we introduced the 'Board set' feature. This feature simplifies the aggregation of Sprint and Kanban metrics for large units by enabling the selection of multiple boards as a single data source with just one click, thereby streamlining the chart creation process.

Release notes

We’ve made some cosmetic changes to help users navigate through new releases and further plans.

Release includes:

• Chart loader with tips
• 'New' label near the version number for the first seven days after release
• Expanded Help menu with new links
• Rate us button

Release notes

We’ve made some cosmetic changes to help users navigate through new releases and further plans.

Release includes:

• Chart loader with tips
• 'New' label near the version number for the first seven days after release
• Expanded Help menu with new links
• Rate us button

Release notes

When exporting a CSV file with chart data for use in external tools or data storage, users often want these numbers to be automatically updated. To address this need, we have developed the Live Data Link feature.

Upon request, the link provides access to the same CSV file as the Export feature. This link facilitates automation by allowing users to obtain real-time updates directly from the chart.

This release includes:

• Live Data Link for Cloud
• Fixed in the Sprint Burndown chart, the issues completed outside are counted as completed

Release notes

When exporting a CSV file with chart data for use in external tools or data storage, users often want these numbers to be automatically updated. To address this need, we have developed the Live Data Link feature.

Upon request, the link provides access to the same CSV file as the Export feature. This link facilitates automation by allowing users to obtain real-time updates directly from the chart.

This release includes:

• Live Data Link for Cloud
• Fixed in the Sprint Burndown chart, the issues completed outside are counted as completed

Release notes

When you have a well-configured gadget for one team or scope, you often want to create a similar one with slight modifications. Before version 6.11.0, this required exporting the settings and importing them into a new gadget while the entire Jira dashboard reloaded multiple times. We understand this was not a pleasant experience.

Therefore, starting with version 6.11.0, you can duplicate your gadget to any dashboard with just a few clicks, eliminating any manual work. Simply click on the button and confirm the selection of the target dashboard.

Release notes

When you have a well-configured gadget for one team or scope, you often want to create a similar one with slight modifications. Before version 6.11.0, this required exporting the settings and importing them into a new gadget while the entire Jira dashboard reloaded multiple times. We understand this was not a pleasant experience.

Therefore, starting with version 6.11.0, you can duplicate your gadget to any dashboard with just a few clicks, eliminating any manual work. Simply click on the button and confirm the selection of the target dashboard.

Release notes

When multiple teams collaborate on, e.g., a major release, having sprint metrics segmented by boards (teams) is essential. This allows you to examine individual team data alongside aggregate values, providing insights into anomalies and trends.

We have introduced this feature exclusively for Team/Cross-team Velocity Chart for Scrum Boards.

Based on your feedback, we plan to extend this functionality to additional charts and include more breakdown options. We would greatly value understanding your specific use cases, so please don't hesitate to contact us!

Release notes

When multiple teams collaborate on, e.g., a major release, having sprint metrics segmented by boards (teams) is essential. This allows you to examine individual team data alongside aggregate values, providing insights into anomalies and trends.

We have introduced this feature exclusively for Team/Cross-team Velocity Chart for Scrum Boards.

Based on your feedback, we plan to extend this functionality to additional charts and include more breakdown options. We would greatly value understanding your specific use cases, so please don't hesitate to contact us!

Release notes

Users of Jira Premium can now create an Issue Hierarchy based on the parent field, which we need to support. Additionally, we have introduced several enhancements to broaden your capabilities.

This release includes:

• Parent field support in Burnup Chart for Initiatives
• Epic filter in Burnup Chart for Initiatives
• Interval Count for sprint grouping by months or quarters
• The average value can be read even with overlaps

Release notes

Users of Jira Premium can now create an Issue Hierarchy based on the parent field, which we need to support. Additionally, we have introduced several enhancements to broaden your capabilities.

This release includes:

• Parent field support in Burnup Chart for Initiatives
• Epic filter in Burnup Chart for Initiatives
• Interval Count for sprint grouping by months or quarters
• The average value can be read even with overlaps

Release notes

Fixed crashed reports if more than one scrum board selected in the settings.

Release notes

• Not finished intervals excluded in forecast calculations based on previous max, min, and average velocity
• Access to settings is available even when the chart is not loaded in reports
• Sprint goals are visible in the “Sprint details” of the chart
• All metrics and essential averages of the Velocity Charts for Scrum
• Boards are enabled by default for all newly created charts
• Added a tooltip to the latest version link
• Added search to the epic dropdown to find any epic without limitation
• Updated UI of the “People” settings tab in the Personal Velocity Chart

Fixes:

• Wrong completed work calculation when choosing more than one status in the custom done statuses field of the Personal Velocity Chart
• Forecast displayed on the chart only after disabling/enabling of the max/min/average labels

Release notes

Fixed crashed reports if more than one scrum board selected in the settings.

Release notes

Improvements:

• Not finished intervals excluded in forecast calculations based on previous max, min, and average velocity
• Access to settings is available even when the chart is not loaded in reports
• Sprint goals are visible in the “Sprint details” of the chart
• All metrics and essential averages of the Velocity Charts for Scrum
• Boards are enabled by default for all newly created charts
• Added a tooltip to the latest version link
• Added search to the epic dropdown to find any epic without limitation
• Updated UI of the “People” settings tab in the Personal Velocity Chart

Fixes:

• Wrong completed work calculation when choosing more than one status in the custom done statuses field of the Personal Velocity Chart
• Forecast displayed on the chart only after disabling/enabling of the max/min/average labels

Release notes

Fixed:

• Forecast being drawn from different dates in the report and gadget
• Wrong forecast calculation when the user selected start burnup "today"
• Different forecasts if applying custom what-if-scenario for the automatically calculated min/max/avg values

Release notes

Fixed:

• Forecast being drawn from different dates in the report and gadget
• Wrong forecast calculation when the user selected start burnup "today"
• Different forecasts if applying custom what-if-scenario for the automatically calculated min/max/avg values

Release notes

To fully implement this blended approach across all charts, we've also incorporated the merger of two types of data — time spent and time remaining — into the Personal Velocity Chart. Utilizing the “Time Spent & Remaining Time” field as an Estimation field allows for comprehensive tracking of a team member’s contributions. This tracking includes their involvement in issues before being unassigned during the sprint, as well as their impact on issues that remain assigned to them after the sprint’s end date.

This release includes:

• Integrated "Time Spent & Remaining Time" Estimation Field in Personal Velocity Chart for Scrum Boards
• Fixed the absence of a message when your license expires
• Fixed that wrong ticket status shown on the chart for tickets with a long history of change logs

Release notes

To fully implement this blended approach across all charts, we've also incorporated the merger of two types of data — time spent and time remaining — into the Personal Velocity Chart. Utilizing the “Time Spent & Remaining Time” field as an Estimation field allows for comprehensive tracking of a team member’s contributions. This tracking includes their involvement in issues before being unassigned during the sprint, as well as their impact on issues that remain assigned to them after the sprint’s end date.

This release includes:

• Integrated "Time Spent & Remaining Time" Estimation Field in Personal Velocity Chart for Scrum Boards
• Fixed the absence of a message when your license expires
• Fixed that wrong ticket status shown on the chart for tickets with a long history of change logs

Release notes

In a Scaled Agile environment, the Jira process needs structuring with complex hierarchies beyond standard offerings. Enterprises adapt by renaming and creating new issue and link types, building an issue architecture above the basic Epic-Story-Sub-task structure.

Adjustments typically involve creating “boxes” for the Program level and “boxes of boxes” for the Portfolio level. Medium-sized businesses may use just one level above the Epic.

In response to many requests to support such structures, we’ve created a new Burnup Chart, which can use any “box” above the Epic level as a data source. To create a chart for a particular scope, you can select the top-level issue for tracking, set the issue level in the hierarchy, and specify the link type to exclude irrelevant links (e.g., “blocked by”)

This release includes:

• New Team/Cross-team Burnup Chart for Initiatives
• The “New” category in Catalog

Release notes

In a Scaled Agile environment, the Jira process needs structuring with complex hierarchies beyond standard offerings. Enterprises adapt by renaming and creating new issue and link types, building an issue architecture above the basic Epic-Story-Sub-task structure.

Adjustments typically involve creating “boxes” for the Program level and “boxes of boxes” for the Portfolio level. Medium-sized businesses may use just one level above the Epic.

In response to many requests to support such structures, we’ve created a new Burnup Chart, which can use any “box” above the Epic level as a data source. To create a chart for a particular scope, you can select the top-level issue for tracking, set the issue level in the hierarchy, and specify the link type to exclude irrelevant links (e.g., “blocked by”)

This release includes:

• New Team/Cross-team Burnup Chart for Initiatives
• The “New” category in Catalog

Release notes

Fixed:

• chart crashes if the sprint contains the issue created after the previous sprint finished
• Sprint Burndown shows a negative Completed Work value

Release notes

Fixed:

• chart crashes if the sprint contains the issue created after the previous sprint finished
• Sprint Burndown shows a negative Completed Work value

Release notes

Integrating Time Spent and Remaining Time gives teams a more nuanced view of workflow, ensuring a smoother transition to Story Points and more accurate forecasting. This release includes a new integrated "Time Spent & Remaining Time" estimation field option for the following charts:

• Team/Cross-team Velocity Chart for Kanban Boards
• Team/Cross-team Burnup Chart for JQL filters
• Team/Cross-team Velocity Chart for JQL filters
• Team/Cross-team Burnup Chart for Kanban Boards
• Team Sprint Burndown Chart

Fixed:

• Charts crash after migration to the new Agile Reports gadget
• Charts are not loaded if the JQL filter with a multi-select custom field is applied
• "Moving average" is incorrect if the number of sprints in the selected average type is bigger than the number of sprints shown on the chart

Release notes

Integrating Time Spent and Remaining Time gives teams a more nuanced view of workflow, ensuring a smoother transition to Story Points and more accurate forecasting. This release includes a new integrated "Time Spent & Remaining Time" estimation field option for the following charts:

• Team/Cross-team Velocity Chart for Kanban Boards
• Team/Cross-team Burnup Chart for JQL filters
• Team/Cross-team Velocity Chart for JQL filters
• Team/Cross-team Burnup Chart for Kanban Boards
• Team Sprint Burndown Chart

Fixed:

• Charts crash after migration to the new Agile Reports gadget
• Charts are not loaded if the JQL filter with a multi-select custom field is applied
• "Moving average" is incorrect if the number of sprints in the selected average type is bigger than the number of sprints shown on the chart

Release notes

Agile Coaches and Scrum Masters are steering their teams through an agile transformation, intending to shift from concrete time measurements to the more fluid concept of Story Points. They're looking to do this in a way that feels natural to the team by drawing on their well-honed abilities to estimate and adjust the time they spend on tasks.

Integrating Time Spent and Remaining Time gives teams a more nuanced view of workflow close to Story Points, ensuring a smoother transition and more accurate forecasting.

This release includes:

• Integrated "Time Spent & Remaining Time" Estimation Field in Velocity, Burnup, and Burndown Charts for Scrum Boards
• Fixed that Average values not exporting to CSV file
• Fixed the absence of dashboards in the list during the migration if the user has more than 100 dashboards on the instance
• Limited to 200 maximum unreleased versions that are loading for validation on the chart view

Agile Coaches and Scrum Masters are steering their teams through an agile transformation, intending to shift from concrete time measurements to the more fluid concept of Story Points. They're looking to do this in a way that feels natural to the team by drawing on their well-honed abilities to estimate and adjust the time they spend on tasks.

Integrating Time Spent and Remaining Time gives teams a more nuanced view of workflow close to Story Points, ensuring a smoother transition and more accurate forecasting.

This release includes:

• Integrated "Time Spent & Remaining Time" Estimation Field in Velocity, Burnup, and Burndown Charts for Scrum Boards
• Fixed that Average values not exporting to CSV file
• Fixed the absence of dashboards in the list during the migration if the user has more than 100 dashboards on the instance
• Limited to 200 maximum unreleased versions that are loading for validation on the chart view

Release notes

In version 6.3.0, we enabled choosing released versions from boards, which caused endless loading and missing chart data. We've rolled back to the old method where only unreleased versions are selectable from the Release dropdown.

To track released versions, try these:

• If a chart was made before a version's release, it'll work unless you change the version in its settings.
• To monitor a particular released version, use the JQL filter in the Issues tab

Release notes

In version 6.3.0, we enabled choosing released versions from boards, which caused endless loading and missing chart data. We've rolled back to the old method where only unreleased versions are selectable from the Release dropdown.

To track released versions, try these:

• If a chart was made before a version's release, it'll work unless you change the version in its settings.
• To monitor a particular released version, use the JQL filter in the Issues tab

Release notes

Now, instead of diving into the edit mode or searching through the chart context menu, just tap on the icon button right from the toolbar.

From version 6.3.0 onwards, you can dive into previous releases to see how things have evolved. It's always good to learn from the past!

Release includes:

• Configuration button in the toolbar
• Past releases selection
• Switching off the active sprint by default

Release notes

Now, instead of diving into the edit mode or searching through the chart context menu, just tap on the icon button right from the toolbar.

From version 6.3.0 onwards, you can dive into previous releases to see how things have evolved. It's always good to learn from the past!

Release includes:

• Configuration button in the toolbar
• Past releases selection
• Switching off the active sprint by default

Release notes

New features:

• Enhanced the Personal Velocity chart with a custom Assignee field configuration
• Velocity and Burnup charts for JQL filters now have a custom Done status configuration

Fixed:

• The closed sprint showed "end date" instead of the actual "complete" date of the sprint

Release notes

New features:

• Enhanced the Personal Velocity chart with a custom Assignee field configuration
• Velocity and Burnup charts for JQL filters now have a custom Done status configuration

Fixed:

• The closed sprint showed "end date" instead of the actual "complete" date of the sprint

Release notes

We've established Dark theme support to align with Jira UI capabilities. Now, using our app is a bit safer for your eyes :)

Since this version, you can create Burnup/Burndown charts across several Scrum Boards and track common Epics or Releases.

Last but not least, we've enhanced creating a gadget on the Jira Dashboard with the same settings as the report, so you don't need to export and import settings manually.

This release includes:

• Dark theme support
• Team Burnup and Burndown Charts for Scrum Boards upgraded to Team/Cross-Team
• Ability to add a report as a gadget to the Jira Dashboard
• Improved error handling in Confluence

Release notes

We've established Dark theme support to align with Jira UI capabilities. Now, using our app is a bit safer for your eyes :)

Since this version, you can create Burnup/Burndown charts across several Scrum Boards and track common Epics or Releases.

Last but not least, we've enhanced creating a gadget on the Jira Dashboard with the same settings as the report, so you don't need to export and import settings manually.

This release includes:

• Dark theme support
• Team Burnup and Burndown Charts for Scrum Boards upgraded to Team/Cross-Team
• Ability to add a report as a gadget to the Jira Dashboard
• Improved error handling in Confluence

Release notes

We've overhauled our chart collection, gadgets, chart settings, and technical architecture to create a completely functional Chart Catalog. Now, both our existing users and newcomers can easily browse the necessary charts and engage with us as assistants for advanced configuration.This release includes:

• Reports and Gadgets revision
• Report UI updates
• Settings updates
• Getting started page
• Chart Catalog
• Create gadget from Catalog
• My Reports button in projects
• Tutorials
• Latest version notification

Read full release notes

We've overhauled our chart collection, gadgets, chart settings, and technical architecture to create a completely functional Chart Catalog. Now, both our existing users and newcomers can easily browse the necessary charts and engage with us as assistants for advanced configuration.This release includes:

• Reports and Gadgets revision
• Report UI updates
• Settings updates
• Getting started page
• Chart Catalog
• Create gadget from Catalog
• My Reports button in projects
• Tutorials
• Latest version notification

Read full release notes

• The percentage value of the "Not completed work" based on the "Final commitment"
• Now, user preferences are enabled for all gadgets in Confluence

Release notes

Improvements:

• The percentage value of the "Not completed work" based on the "Final commitment"
• Now, user preferences are enabled for all gadgets in Confluence

Release notes

Fixed:

• Metrics values in 'active sprint' were not being rounded correctly
• The chart crash after executing specific JQL filter

Release notes

Fixed:

• Metrics values in 'active sprint' were not being rounded correctly
• The chart crash after executing specific JQL filter

Release notes

Fixed chart settings migration during an update to the latest version from an app version 3.5.16 and older

Release notes

Fixed chart settings migration during an update to the latest version from an app version 3.5.16 and older

Release notes

• Fixed the recent reports' broken link
• Added pagination to the saved JQL filter selector

• Fixed the recent reports' broken link
• Added pagination to the saved JQL filter selector

Fixed the Velocity chart does not show re-assignee for a ticket in the active sprint

Fixed the Velocity chart does not show re-assignee for a ticket in the active sprint

Fixed issue with JQL filter type for Business charts

Release notes

Fixed issue with JQL filter type for Business charts

Release notes

Fixed:

• "Completed Outside" metric not moving to "Completed" after issue was reopened
• metrics are not displayed in charts with an Epic filter selected

Please see the release notes.

Fixed:

• "Completed Outside" metric not moving to "Completed" after issue was reopened
• metrics are not displayed in charts with an Epic filter selected

Please see the release notes.

Fixed the Kanban Team Velocity is not showing Assignees in the charts

Release notes

Fixed the Kanban Team Velocity is not showing Assignees in the charts

Release notes

Updated Atlassian-related dependencies to the latest versions.

Updated Atlassian-related dependencies to the latest versions.

Performance improvement for Business Team Velocity and Business Team Burnup charts

Release notes

Performance improvement for Business Team Velocity and Business Team Burnup charts

Release notes

Fixed the issue with cache state replication across Jira nodes for invalidation operations

Release notes

Fixed the issue with cache state replication across Jira nodes for invalidation operations

Release notes

Fixed:

• incorrect metrics calculation for completed work (initial) when estimation changes
• 403 error appearing inserting a macro into a Confluence page

Release notes

Fixed incorrect metrics calculation for completed work (initial) when estimation changes

Release notes

Fixed wrong user names labels on Personal Velocity Chart

Release notes

Fixed wrong user names labels on Personal Velocity Chart

Release notes

New feature:

• Custom estimation field for particular Scrum Board in Cross-team Velocity Chart

Bug fix:

• Issues show unassigned as assignee in Velocity Chart for Kanban team

Read more

New feature:

• Custom estimation field for particular Scrum Board in Cross-team Velocity Chart

Bug fix:

• Issues show unassigned as assignee in Velocity Chart for Kanban team

Read more

• Enable / Disable cache

Fixed:

• Gadget crashing with only one interval at the report

Release notes

New feature:

• Enable / Disable cache

Fixed:

• Gadget crashing with only one interval at the report

Release notes

• New charts: Scrum Cross-team Velocity Chart, Scrum Personal Velocity Chart
• New features in Scrum Team Velocity Chart: default estimation, percentage base, custom Done statuses, group sprints

Release notes

• New charts: Scrum Cross-team Velocity Chart, Scrum Personal Velocity Chart
• New features in Scrum Team Velocity Chart: default estimation, percentage base, custom Done statuses, group sprints

Release notes

The user can see charts faster.

Release notes

The user can see charts faster.

Release notes

Improvements:

• Polished mechanic for custom JQL auto-suggestions
• Changed rounding of estimation values to 2 digits

Release notes

Improvements:

• Polished mechanic for custom JQL auto-suggestions
• Changed rounding of estimation values to 2 digits

Release notes

New major features:

• Improved UI/UX - analyse the reports more efficiently
• User Preferences - customise the metrics that you want to see on the chart without affecting the chart’s look and feel for other users

Release notes

New major features:

• Improved UI/UX - analyse the reports more efficiently
• User Preferences - customise the metrics that you want to see on the chart without affecting the chart’s look and feel for other users

Release notes

• Done issues duplicate in intervals
• Not all resolved issues are included in the chart

Release notes

Fixed:

• Done issues duplicate in intervals
• Not all resolved issues are included in the chart

Release notes

• Some sprint tickets are not displayed on the charts

Release notes

Fixed:

• Some sprint tickets are not displayed on the charts

Release notes

• Epic field is reset when the settings menu is opened in Burnup & Burndown charts
• Not all resolved resolved issues are included to the Universal\Business Velocity Chart
• Request header too long issue

Improvements:

• New branding logos
• Export files content cleanup

Fixes:

• Epic field is reset when the settings menu is opened in Burnup & Burndown charts
• Not all resolved resolved issues are included to the Universal\Business Velocity Chart
• Request header too long issue

Improvements:

• New branding logos
• Export files content cleanup

Release notes