Can you please guide me on how to locate the closed Jiras for each sprint in a team-managed project?

[Kamalkumar S_ Chandran]

Hi,

I am trying to create a report with the number of Jiras closed per sprint. But there is no option available. Can someone let me know the steps.

Thanks in advance!

Best regards,

Kamalkumar S. Chandran

[Walter Buggenhout]

Hi @Kamalkumar S_ Chandran and welcome to the Community!

Let me suggest 2 approaches. If you want to see get a good overview of what happened in a specific sprint, you can look at the Sprint Burndown Chart that is available from the reports section in your project.

In that report, there is a list of all completed issues in the sprint, as you can see in this example:

Interesting about the report, is that there's plenty of other information available as well, such as scope change, issues that were not completed or completed outside of the sprint.

This does not give you an overview of issues completed in multiple sprints. So a potential approach would be to create a filter of all completed issues in your team managed project and use that to visualise the data on a Jira Dashboard.

The following filter would return all resolved issues in your project:

Project = TMSD AND resolution is not empty

Save that filter, create a Jira Dashboard and add a gadget to it to display the result graphically. In this example, I used a pie chart gadget, sliced by sprint:

You can use other types of gadgets as well of course, but the principle remains the same. Add a gadget, select your saved filter as input source for the gadget and make sure to use sprint as the element to divide your data.

Hope this helps!

[Kamalkumar S_ Chandran]

In the pie chart gadget, spillover Jiras are coming in all the sprints in which the it is part of.

[Walter Buggenhout]

Yes @Kamalkumar S_ Chandran, that is a correct observation. As I mentioned, the sprint report has the exact details, but it can only be viewed one sprint at a time. The out-of-the-box gadgets in Jira let you create overviews across multiple sprints, but they have this limitation indeed.

To create a nice overview of all issues closed in a sprint, you would need a more powerful reporting solution that can handle these historic data better, such as e.g. EazyBI. In this demo account you can see an example of what you are trying to achieve:

The sample report is showing story points, but you can display issues instead as well.

[Kamalkumar S_ Chandran]

Thanks a lot Walter Buggenhout