Fixed:
- gadgets displaying an error screen in Wallboard mode
- macros crash for cases when the double space in sprint goals
Fixed:
Updated Atlassian-related dependencies to the latest versions.
Updated Atlassian-related dependencies to the latest versions.
Fixed the issue with cache state replication across Jira nodes for invalidation operations
Fixed the issue with cache state replication across Jira nodes for invalidation operations
Fixed macros crash for cases when the double space in sprint goals
Fixed macros crash for cases when the double space in sprint goals
Fixed wrong user names labels on Personal Velocity Chart
Fixed wrong user names labels on Personal Velocity Chart
Added the ability to choose custom estimation fields for cases when, for example, one team uses the “Story Points” field, and all others use “Story Point Estimate”.
Added the ability to choose custom estimation fields for cases when, for example, one team uses the “Story Points” field, and all others use “Story Point Estimate”.
New feature:
Fixed:
Fixed:
Fixed:
Fixed sprint order for Team Velocity Chart
Fixed sprint order for Team Velocity Chart
Fixed:
Implemented:
Fixed:
Improvements:
Improvements:
New major features:
New major features:
Fixed:
Improvement:
Fixed:
Fixed:
Fixed:
Fixed completed work not counted in metrics for sub-tasks
Fixed completed work not counted in metrics for sub-tasks
Implemented:
Fixed:
Improvements:
Visit release notes confluence page to see more details.
Implemented:
Fixed:
Improvements:
Visit release notes confluence page to see more details.
Fixed:
In this release we have added the following features and made some improvements to gadgets editing:
In this release we have added the following features and made some improvements to gadgets editing:
New feature:
Fixed:
New feature:
Fixed:
Fixed:
Fixed:
Fixed:
Fixed:
Fixed:
Fixed:
Fixed:
Fixed:
Features:
🇺🇦🇺🇦We @ Broken Build the Ukrainian company stop support and blocked apps and sales for clients from Russia and Belarus in response to their aggression against Ukraine🇺🇦🇺🇦
Features:
🇺🇦🇺🇦We @ Broken Build the Ukrainian company stop support and blocked apps and sales for clients from Russia and Belarus in response to their aggression against Ukraine🇺🇦🇺🇦
Fixed:
Fixed:
In this major new version 4.0 of Velocity Chart app we have added a new gadget - Personal velocity chart. Using this gadget you can check the individual velocity of all users that contributed to a sprint.
Now Velocity Chart Gadget app covers all velocity reporting levels:
In this major new version 4.0 of Velocity Chart app we have added a new gadget - Personal velocity chart. Using this gadget you can check the individual velocity of all users that contributed to a sprint.
Now Velocity Chart Gadget app covers all velocity reporting levels:
Fixed:
Fixed:
Fixed:
Fixed:
Fixed:
Fixed:
In this release we have fixed an issue with Initial commitment metric calculated as 0.
In this release we have fixed an issue with Initial commitment metric calculated as 0
In this release we have added the following features:
In this release we have added the following features:
In this release we have added the ability to configure issue statues in which issues are considered as completed and counted in Completed work.
By default Completed work is calculated for the issues in statuses that are mapped to the last Agile Board column. Using the new configuration option "Done status mode" you can switch from default to custom status selection.
In this release we have added the ability to configure issue statues in which issues are considered as completed and counted in Completed work.
By default Completed work is calculated for the issues in statuses that are mapped to the last Agile Board column. Using the new configuration option "Done status mode" you can switch from default to custom status selection.
In this release we have added new sprint metric to calculate the completed work which was part of initial commitment called "Completed work (initial)".
We have also fixed aggregated sprint dates in CSV export of Enterprise Velocity Chart.
In this release we have added new sprint metric to calculate the completed work which was part of initial commitment called "Completed work (initial)".
We have also fixed aggregated sprint dates in CSV export of Enterprise Velocity Chart.
In this release we have added the ability to export sprint issues in JSON format for customer support purposes. The export button is located next to sprint name on sprint issue details panel. Exported issues do not contain any text information like summary, description etc and can be safely sent to our support team. Using this data we would be able to investigate and fix calculation issues much faster.
We have also fixed and issue with IE11 browser.
In this release we have added the ability to export sprint issues in JSON format for customer support purposes. The export button is located next to sprint name on sprint issues details panel. Exported issues do not contain any text information like summary, description etc and can be safely sent to our support team. Using this data we would be able to investigate and fix calculation issues much faster.
We have also fixed an issue with IE11 browser.
In this release we have fixed an incorrect "Not completed work" sprint metrics calculation when in some cases it was displayed as a negative value.
In this release we have fixed an incorrect "Not completed work" sprint metrics calculation when in some cases it was displayed as a negative value.
JQL filter:
In this release we have made a lot of small improvements:
Bug fixes:
In this release we have made a lot of small improvements:
Bug fixes:
Fixed:
Fixed:
In this release we have added a new velocity gadget called Enterprise Velocity Chart. Using this gadget you can get aggregated metrics overview over multiple teams. The use case is when several teams are working on a product the gadget aggregates parallel sprints into super-sprint and generates super-sprint metrics on a product level automatically. You no longer need to calculate those aggregated product statistics manually.
New features for Agile Velocity Chart:
In this release we have added a new velocity gadget called Enterprise Velocity Chart. Using this gadget you can get aggregated metrics overview over multiple teams. The use case is when several teams are working on a product the gadget aggregates parallel sprints into super-sprint and generates super-sprint metrics on a product level automatically. You no longer need to calculate those aggregated product statistics manually.
New features for Agile Velocity Chart:
Fixed:
Improved:
Fixed:
Improved:
Fixes:
Fixes:
Completion % is now calculated for both Initial and Final commitment in CSV exported data
Completion % is now calculated for both Initial and Final commitment in CSV exported data
Using this version you can now browse sprint issues as if you were using the built-in Sprint Report:
Read our short blog post for more details.
Using this version you can now browse sprint issues as if you were using the built-in Sprint Report:
Read our short blog post for more details.
Improvements
Improvements
In this release we have improved the way how average values for sprint metrics are calculated:
We have also fixed label values with proper rounding.
In this release we have improved the way how average values for sprint metrics are calculated:
We have also fixed label values with proper rounding.
This is a major new version 2.0 with the following new features:
This is a major new version 2.0 with the following new features:
Fix 'Edit' action in gadget menu is available for users without manage dashboard permission
Fix 'Edit' action in gadget menu is available for users without manage dashboard permission
Handle case and show user-friendly error message when there are no Scrum boards available
Handle case and show a user-friendly error message when there are no Scrum boards available
In this release we have added a new configuration option to exclude sprints with zero metric value from its average calculation.
In this version we have added ability to configure an average line visibility per sprint metric rather than show/hide averages globally for all enabled metrics.
Please read our blog post for more details.
In version 1.9.0 we have added a new stack bar chart type.
With the new chart type option sprint metrics are displayed as stack bar by default. You can optionally switch any metric to be displayed as a line.
Please refer the documentation for more details.
In this release we have added several new features to show additional sprint details:
You can configure which data to show and in which order (for bar charts).
All those details can now be displayed for active sprints too if 'Show active sprints' option is enabled.
CSV data export includes all new details which can be further processed, converted or shared.
You can find more details and screenshots in our blog post.
In this release we have added an option 'Time unit' to show velocity in days or hours. It is available for boards with 'Original time' estimation. If tasks have large estimates then days are much easier to read.
Number of hours in working day is based on global Jira time tracking settings.
Planned sprint velocity is now calculated correctly when issues were added/removed from active sprint.
In this release we have simplified providing technical data gadget is based on to our support team. This will help us to investigate and fix any reported issues faster.
The support screen contains support contacts and links as well as technical data which can be reviewed and adjusted before sending.
Just click 'Get support' on a gadget view screen and copy&paste the technical data into the support email or Jira Service Desk support ticket.
We have fixed an invalid value labels position which should follow custom bars order.
In this release we have added a new configuration option "First bar" with two options 'Planned' and 'Completed' to define order of velocity type bars.
We have also fixed an issue with long sprint names partly hidden when displayed as x-axis labels.
In this release we have improved the flexibility of working with large number of sprints. Jira administrator can now define global limit for max possible sprint count in all gadgets.
By default the limit is not defined. If you are Jira administrator and want to configure the settings you can do so via 'Configuration' link after upgrade to this version which points to a new app configuration page in Apps administration area.
Please share your feedback with us via support@brokenbuild.net
In this release we have added an option to configure the number of sprints to be displayed. That wouldn't make sense if the max number of sprints were 7 like in standard JIRA Software Velocity report.
That's why the gadget now supports the complete board sprints history and it is up to how many to show (the default value is still last 7)
Please send us your feedback to support@brokenbuild.net
In this release we have added new configuration option "Show value labels" to display sprint velocity values and average velocity values as labels on a chart.