Flow Velocity

[alex]

I'm trying to set up a dashboard that will show me flow velocity across teams.  I have jira advanced roadmaps in the cloud if that matters.  I am trying to use the two dimensional filter gadget to show the count of story points on completed tickets w/in a time period (sprint).  The custom field 'story points' which is a numbered field, is not showing up when I go to configure the widget.  How can I make this field visible?  Is there another way I can see total completed story points for a team in a given sprint?

[Danut M _StonikByte_]

Hi @alex,

Try the velocity gadgets offered by our Great Gadgets app. 

With these gadgets you can track the velocity for each individual team and the velocity at the global level (cross-team/project). The gadgets are highly configurable and support any type of estimate, including  numerical custom fields.

Team Velocity gadget - to track sprint velocity for every team

Kanban Velocity gadget - to track velocity for past intervals for every team or at the global (cross-teams) level

Please note that this app offers many other gadgets for tracking agile projects. It can be a great asset for your company. 

Have a look over the articles from our blog to see how many things you can track with this app. 

I hope this helps. If you have any questions, please don't hesitate to contact us at support@stonikbye.com.

Thank you,

Danut Manda

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

The filter statistics gadgets are for grouping together and counting issues grouped by a known value, which means they can only work off issue fields that have known lists of options.  A number field such as story points is not a list field, so you can not use it for grouping.  

There are other problems with asking for this report.

Each team should be running their own separate sprint, so even if you could use story points as an axis, you would end up with something like

	Team A	Team B	Team C
Sprint for team A	14 issues	0	0
Sprint for team B	0	12 issues	0
Sprint for team C	0	0	19 issues

One team's story points are often different to another.  When I was last a part of a developer team, we regularly estimated issues to be 5 or 8 story points and suggested that another team took them because they had better expertise in the subject, and they usually took the estimate down by 2-3 story points if they took them on.  Unless you also have an organisation-wide mandate that story points across teams all represent the same levels of complexity, then you will find that story points are going to differ between teams even when the teams have the same expertise.

You should be looking at the sprint reporting for this, not filter statistics.