nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to create a story burnup (total created and total resolved) by week

Broussard, Anna

I am able to create a story burnup with 2 series, total created and total resolved by week. I don't really care about sprints, but rather I want to see total for my project over a time range. My chart is based on story created date, so even if the story was created in week 1, and story point was added in week 3, my chart will show the increase in week1. How do I get a burnup based on when the story points were added?

Accepted answers

Jessie Turpin

Hi @Broussard, Anna you'd probably want to use the Issue history table to capture when the story points were added to an issue. The screenshot below is an example of which columns you could include from the Issue history table to gather the day when the story points were added to an issue.

Screenshot 2025-05-02 at 4.35.50 PM.png

Then, you'd only need to adjust your chart to use the data from this query to calculate the burnup with your story point values.

All comments

Danut M _StonikByte_

Hi @Broussard, Anna,

I am not very familiar with the Analytics, but could eventually try using a cumulative chart or stacked Areas, by Story Points.

If you don't manage to figure it out in Analytics, you could look for Jira apps on Atlassian Marketplace that provides this type of chart.

If you consider the idea of using an app, this can be easily achieved by using some of the gadgets offered by our Great Gadgets app.

Release Burndown Burnup Chart gadget - lets you generate the burnup. All you have to do is to configure it with a filter/JQL that returns your issues, calculate by SPs, set the timeline and group data by 1 week.

Cumulative Flow Diagram gadget - lets you generate a cumulative stack area chart based on the story points of the issues from filter/JQL, grouped weekly and split by status category.

Danut.

Jessie Turpin

Screenshot 2025-05-02 at 4.35.50 PM.png

Then, you'd only need to adjust your chart to use the data from this query to calculate the burnup with your story point values.

Broussard, Anna

Thanks @Jessie Turpin , I was able to do what you suggested. I think the hurdle is knowing how to build increasingly complicated scaffolding. For example, I started with stories created and resolved by created and resolved week, then realized that doesn't really represent when the team actually planned out their story points, so I need this query, which isn't really well documented, then I have to capture the stories that have transitioned from other issue types (like question->story or task->story), which probably means I need another issue history processing, then I want to filter by fix version and other field filters. It would be helpful if Analytics could supply some basic measures of story points history, created vs resolved, and straightforward use cases that are meaningful to a technical or program manager to get project health trends.

Jessie Turpin

Thank you for your feedback @Broussard, Anna! You're correct that we unfortunately don't have any chart templates specifically focused on story points that isn't a sprint metric. I'll pass this feedback along to our team though