Build reports based on closed Sprint data snapshots

[Yury Belezyak]

Dear community,

I have an idea to build a report that would display:

- Count of issues in each Status

- For all closed sprints

- With data that was at the moment of Sprint Closure (same as we get from Sprint report Jira feature)

The result should be also expressed as a line graph where I would see lines for each sprint that show number of issues per Status.

The initial idea was to use plug in, but most of them cannot gather historical information of Sprints.

Any idea on possible plug-in or another solution?

(Power BI may work, but I am not sure 100%)

[Danut M _StonikByte_ · Accepted solution]

Hi @Yury Belezyak,

I don't see a way to do this with Jira native reports or gadgets.

But you will be able to generate such report and charts by using the gadgets offered our Great Gadgets app. 

For example, to see the number of issues in DEV test column at the end of each sprint, based on historical data, you could use the Team Velocity gadget configured to consider as "done" that issues in the statuses mapped on your Dev Test board column.

To achieve this:

• add Team Velocity gadget to your dashboard
• select the board and specify the number of past sprints to be displayed
• configure it to display only Completed series
• on its More settings tab, at "Done means" select the statuses mapped on your Dev Test board column
• Check "Display all series as lines" if you prefer line chart instead of bar char
• Check "Show data table" for the gadget to display a Data tab with a report listing the Dev Test issues in every sprint 

The same app also offers a Pivot Table & Pivot Chart gadget, which can easily generate data in the desired format, but it doesn't use historical data. But even so, it might be worth a try, perhaps it helps in some extent.

If you need any assistance in configuring these gadgets, feel free to contact our team at support@stonikbyte.com.

Danut.

[Yury Belezyak]

Thank you! Seems like should work. Will try today

[Yury Belezyak]

@Danut M _StonikByte_ 

Thank you again for recсomendation. It is still not perfect but matches the need. However, there is one thing I not sure if I can do. Can you please assist me on that? 

I want to see how precise time estimations are in the team. So, I need to take original time estimate and subtract time difference between two custom fields (start date and end date). 

Is there a way to do so with your gadget? 

[Danut M _StonikByte_]

Hi @Yury Belezyak,

Unfortunately it is not possible to make the difference between two date fields by using the gadgets.

But you could have this calculated on a per issue basis and stored in a separated  issue custom field via Jira Automation. Then, use this field in the gadgets for stats. 

I don't have too much experience with Jira Automation, but there are many articles in the Community that could be helpful. See some examples.

https://community.atlassian.com/t5/Jira-questions/automation-for-date-difference/qaq-p/2343981

https://community.atlassian.com/t5/Jira-Service-Management/Calculate-the-difference-between-two-custom-fields/qaq-p/2233212

Danut. 

[Yury Belezyak]

Actually yes, thank you for mentioning. 

Sure I can do that. I just forgot :)

[Alexey Pavlenko _App Developer_]

Hi @Yury Belezyak ,

Unfortunately, JIRA doesn't provide this functionality natively. You need 3rd party app for that. You use try the one I developed -  Multi-team Scrum Metrics & Retrospective. It doesn't have line graph actually - only bar chart, but it provides a lot of features for the analysis and retrospection. Here is the view you can get with it:

 

Columns are adjustable. Also, you can track any custom JQL metric here.

Best regards,
Alexey

[Shivam Sharma]

Hi @Yury Belezyak ,

For generating a report that shows issue counts by status at the moment of sprint closure (similar to Jira's Sprint Report) and visualizing it as a line graph.

You might want to try Report X, a plugin designed for multilevel traceability reports. While we’re actively working on enhancing it to fully address your specific scenario, you can already create a similar report by:

• Adding two group by clauses:
  1. Sprint
  2. Status
• Using the Sum Up operation to count issues.

We would appreciate your feedback or suggestions as we continue to enhance Report X.

[Yury Belezyak]

Thank you for a suggestion. I will review the app later, as I see that it will not meet my expectations for now. 

[Dave Mathijs]

Hi @Yury Belezyak welcome to the Atlassian Community!

• What would be the objective of this report?
• Where do the default available reports and insights not meet your current requirements?

In the end, you want to know if you have achieved the sprint goal (vs. committed). For issues that weren't closed at the time of sprint closure, does it matter what the status was at that point-in-time (to do vs. in progress)?

You either move them to the next sprint or they go back to the backlog.\

I'm just curious about the why.

[Yury Belezyak]

Hi @Dave Mathijs 

The main objective is to figure out Sprint bottlenecks and get insides on actual capacity for team members.

So that we could easily see that for example DEV test column usually has a lot of unclosed tickets at the end of each sprint. Additionally, I want to see the tendency over the last sprints without opening several Sprint report pages.

As we are having only 1 person for code reviews and testing, I would like to address this report to justify new job openings to our team. 

The built-in Sprint report is great but, doesn't give a line graph and no easy way to compare 2 or more sprints. 

[Dave Mathijs]

Thanks for the clarification. If you're considering a third-party app, I'd recommend having a look at Nave.

[Yury Belezyak]

I'll take a look, thank you!