Report of closed issues per sprint per project

[Antonio Bojorges]

Hello!

I have multiple projects that have epics linked to ideas in a Discovery project. I want to be able to do 2 things:

• Have a report to allow me to see all issues (epics, stories, features, etc) with the sprint in which they were closed. Today I can download all issues in a csv, but I can see all sprints they were open through, but it's not easy to know which one was the last one, or the one they were closed (because sprints are all in different columns). The goal of this is to see number of issues and story points closed per assignee, per project, per sprint.
• If there's a way to automate the first point, where I could see a list of assignees per project, per sprint and see how many issues or story points they've closed

This might be a lot, but wondering if there's a tutorial about this.

Thanks!

[Valeriia_Havrylenko_SaaSJet]

Hi @antonio_bojorges  👋

Welcome to the community! 

For displaying report of closed issues per sprint per project i suggest you to try Time In Status for Jira add-on. Primary propose of our tool is generating reports that show how much time each issue has spent on each status, assignee, team, or project. Also we have Sprint Performance Report which contains various metrics for each sprint. 

 I would be happy if you had a look at it! 

Try Time In Status for Jira for free.

You can also book a live demo - we'll show you the application inside out and answer all your questions.

Have a nice day and happy sprinting 🥳

[Hannes Obweger - JXL for Jira]

Hi @antonio_bojorges

welcome to the community!

If you're open to solutions from the Atlassian Marketplace, I think you might like the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of so-called smart colums that aren't natively available - like e.g. the issue's last sprint - as well as a number advanced features, including support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

With these, you can build a view like e.g. this in just a couple of clicks:

This is really just one of virtually endless possible reports; you can also group by any other issue field(s), use different sum-up techniques, etc. etc.

Any questions just let me know,

Best,

Hannes

[Mary from Planyway]

Hi @antonio_bojorges 

It's Mary from Planyway for Jira: roadmap, workload, time tracking.

Creating a report in JIRA to see all issues with the sprint in which they were closed, and automating the process to track the number of issues and story points closed per assignee, per project, per sprint involves a combination of JIRA's querying capabilities, possibly some custom scripting or integration with JIRA's API, and leveraging JIRA's reporting and dashboard functionalities. 

1. Creating a Custom Report for Closed Issues by Sprint

Using JQL 

1. Identify Closed Issues: Use JQL to filter issues that are closed. You can specify the project, issue types (Epics, Stories, Features, etc.), and the status (e.g., "Done" or "Closed").
   project = "YourProjectKey" AND issuetype in (Epic, Story, Feature) AND status = Closed
2. Extract Sprint Information: Extracting the last sprint information for each issue directly via JQL is challenging because JQL doesn't natively support this level of complexity. You'll typically see all sprints an issue has been part of, not just the closing sprint.

Using Reports and Dashboards

• Sprint Report: Use the Sprint Report in JIRA to view issues completed in a specific sprint. While this doesn't directly solve the multi-project view, it's a start for per-sprint analysis.
• Dashboards: Create a dashboard and add gadgets that display issues filtered by your JQL queries. You might not find a gadget that shows exactly what you want (e.g., last sprint closed), but you can get close with some configuration.

Exporting Data for External Analysis

• Export to CSV: Since you already can export issues to CSV, you might continue to do so and then use external tools like Excel or Google Sheets to analyze which sprint was the last one an issue was part of. You could use formulas or scripts within these tools to parse the sprint information from the exported data.

2. Automating the Reporting Process

Using JIRA's REST API

For automation, consider using JIRA's REST API. You can write scripts (in Python, for example) to query JIRA's REST API to fetch issues based on your criteria, extract the relevant sprint information, and compile the data into reports.

• Fetch Issues: Use the /search endpoint with your JQL query to get issues.
• Parse Sprint Information: Extract the last sprint information from the issue's field data. This will require parsing the issue fields, which might involve some complexity depending on how your sprints are recorded in JIRA.
• Generate Reports: Aggregate this data to calculate the number of issues and story points closed per assignee, per project, per sprint. You can then output this to a format of your choice (e.g., CSV, Excel, a custom web dashboard).