How can I see historical tracking for points completed per person each sprint?

Question

Looking to create a Dashboard on Jira that allows me to see a historical tracking of points completed by person each sprint. I thought the Kanban Velocity/Throughput Gadget would be helpful, but I'm not figuring out how to see it by person. This is showing the whole team's throughput.

Marlene Kegel - codefortynine · Answer

Hello @Heidi Vanderholm,

I am Marlene, product manager of Quick Filters for Jira Dashboards.

With our app you can create a Two Dimensional statistic which can display the number of story points per assignee in each sprint.

You could also configure it differently and use the Quick Controller gadget to filter your dashboard gadgets dynamically, e.g. per assignee or sprint.

You can test Quick Filters for Jira Dashboards without installation on our demo dashbaords.

Danut M _StonikByte_ · Answer

Hi @Heidi Vanderholm,

This is not possible with Jira's default gadgets.

But you could try the Pivot Table & Pivot Chart gadget offered by our Great Gadgets app. It can display the story points completed by every person in past sprints in multiple ways:

As table

As heatmap table

As charts of various types

Steps for configuring this:

1. Configure the gadget with a filter or JQL that returns done issue:

statusCategory = Done

2. Select fields to be used: Sprint, Assignee and Story Points

3. Configure the pivot table to display data like this:

Note: For this info to be accurate, once a story has been completed it must not be reassigned or re-estimated after sprint completion.

See also this article for more examples: https://community.atlassian.com/t5/Jira-articles/Building-a-powerful-Kanban-dashboard-in-Jira-with-Great-Gadgets/ba-p/1664331.

Danut

Bill Sheboy · Answer

Thanks for that additional information.

As this sounds like a one-off for reporting, perhaps export a few sprints of data to a spreadsheet and create a simple pivot table.  Once the team decides on a next, starting point for forecasting, the team velocity chart could be used going forward...along with discussions at the retro about "what happened" and how to experiment with forecasting for more improvements.