Reporting: Story points resolved over time (e.g. per week)

Question

Hi there,

We currently use Story Points in our issues to determine the workload of an issue. 
In our very specific example we use our board for training program planning and we use Story Points for the number of training programs we plan.

As a ticket/issue can vary from 1 training session to >100 training sessions, we would like a way to report not only how many tickets/issues were resolved per week, but we would like to see how many Story Points were resolved in a week.

Does anyone know how we can use Jira Reporting to show us how many Story Points are resolved?

On the screenshot you can see the Story Points yellow marked:

Daina Tupule eazyBI · Answer

eazyBI app supports creating various custom charts on Jira data. You can analyze Story points by creation and resolution date. See my report example:

You can build many more different metrics based on Story Points and other issue data. See our demo account for some example reports on story points and issues for inspiration.

Daina / support@eazybi.com

Bill Sheboy · Answer

Thanks for clarifying, @Nynke Polet

You are describing a throughput chart for a Kanban team, counting based upon sum of the estimate/week (e.g. story points/week) and displayed over time.

Unfortunately that is not available with out-of-the-box Jira Cloud. You can see the count of issues done per week with Atlassian's interpretation of a Cumulative Flow Diagram (CFD), but the y-axis cannot be changed to story points.

There are a few other options you can investigate, based upon your cost/easy of use/frequency of use needs:

* monthly costs, possibly easy to use, needed often:* Investigate the marketplace to purchase apps for dashboard gadgets

* free, build it yourself, needed one time:* download your issues to a spreadsheet, and use formulas or a pivot table to plot over time (e.g. sum of story points and resolved date)

* free, build it yourself, needed often:* use the free Google Sheets or Excel addons for Jira, pull your data, and report it when needed.  The advantage of this over the second option is that it can preserve your JQL query and pull in more data.

Nynke Polet · Answer

Hi Bill,

Thanks for your quick reply.

Hereby a clarification from my side: 
1. Our training programs contain 1 or more training sessions - this can be a small program with 1-3 training sessions for our clients to very large programs, containing for example 20 programs of 5 or 6 training sessions. We plan per 'sold program', which means that we plan all training sessions at once. They will be facilitated over the course of a longer time but in Jira we only keep track of number of training programs and training sessions that we have planned. 
2. We are keeping the Story Points per issue always the same, as that program contains a certain amount of training sessions. 
3. After program planning we decompose the programs and work to be done into a different system where we can let it go through our program execution flow. The only tracking of workload we currently have in Jira is # of tickets and the Story Points, with the Story Points being the best indicator of workload.

Do you think there is a way to report on number of Story Points?

Looking forward to hearing your thoughts! And please let me know if I should clarify further.

Kind regards, 
Nynke