Automating Weekly Sprint Metrics Generation in JIRA

Hi there!

I need help with creating automated reports for my team. Every week and after each sprint ends, I have to pull together a bunch of different metrics manually and it’s taking way too much time.

Here’s what I need to track:

  • Tasks planned vs tasks with no remaining effort
  • Finished items with zero remaining work
  • Sprint completion percentage
  • Outstanding work items
  • Finished remaining tasks
  • Completion rate for remaining work
  • Level 1 item completion rate (User Stories & Tasks)
  • Level -1 item completion rate (Sub-items)
  • Total bug count
  • Resolved bugs
  • Average bug fix duration
  • Team velocity metrics
  • Cycle time analysis
  • Blocked items resolved

We use Original Time Estimate instead of Story Points in our workflow. I’ve tried building a basic filter but it’s not giving me everything I need:

project = MyProject AND Sprint = "Current Sprint Name"

AND created <= "Sprint End Date"

AND issuetype != Sub-task

AND statusCategory != Done

I’ve experimented with Google Sheets integration and some JIRA add-ons but haven’t found the right approach yet. Has anyone solved something similar? Any suggestions for filters or tools that could help automate this reporting process would be awesome.

Thanks!

We hit this same headache last year. Skip the master filter approach - it’s a pain. I made separate saved filters for different metrics and threw them all on a dashboard using JIRA’s gadgets. Way cleaner. For completion rates and velocity, I used ScriptRunner to set up calculated fields. They auto-compute percentages from your Original Time Estimate values. Game changer. The trick is making a separate filter for historical data that pulls from closed sprints. That’s where you get your trends. Bug metrics get their own filter too - group by resolution date and use JQL functions for averages. Took me three days to set up, but now sprint retros are automatic. No more manual number crunching. Also check JIRA’s built-in burndown reports - they already track some of this stuff.

honestly, you need eazyBI or smth similar instead of hacking filters together. we switched from manual reporting last year and it was a game changer - pulls all those metrics automatically once you configure it properly.

Had this exact problem six months ago - manual sprint reporting was killing me. Here’s what worked: I built a simple Python script that hits JIRA’s REST API weekly via cron job. The trick is splitting your metrics into separate API calls instead of cramming everything into one filter. For velocity and cycle time, I pull historical sprint data and calculate averages in the script. Bug metrics need their own queries filtering by issue type and resolution dates. Everything dumps to CSV that feeds our dashboard. Took about a week to set up, but now I get comprehensive reports without touching anything. If you don’t want to script, check out Atlassian Analytics - it handles the API stuff for you.