Skip to content
← bytera.tech Bytera Docs

Sprint Autopsy

When a Jira sprint moves to Closed, SyncUp listens to the avi:jira-software:closed:sprint event and generates a structured Sprint Autopsy report. The report is saved to Forge SQL and immediately available in the Reports tab.

Sprint Autopsy report

Where to find autopsies

Section titled “Where to find autopsies”

Open the Reports tab in SyncUp. You’ll see a list of every sprint we have a report for, each row showing:

  • Sprint name
  • Final Health Score badge (Healthy / At Risk / Critical)
  • Items delivered vs planned (e.g. 12/15 delivered)
  • A scope-change lozenge (e.g. +18% scope) when scope grew

Click any row to drill into the full report.

If you have at least two reports, a 📊 Sprint Comparison table appears beneath the list, comparing your last five sprints side-by-side.

What’s in an autopsy

Section titled “What’s in an autopsy”

Each report has six sections, all derived from the issues that were in the sprint plus the snapshots collected through it.

1. Delivery

Section titled “1. Delivery”
  • Planned items — count at the earliest snapshot.
  • Completed items — how many ended in a Done category.
  • Carried over — planned but not done.
  • Completion % — completed / total.
  • By priority — a breakdown of how each priority level performed.

2. Scope Change

Section titled “2. Scope Change”
  • Initial total vs final total.
  • Added — items added after sprint start.
  • Change % — added / initialTotal × 100.

3. Flow Metrics

Section titled “3. Flow Metrics”
  • Average cycle time in hours and days — how long, on average, a delivered item took from created to updated-after-Done.
  • Throughput — total completed items.
  • Daily throughput — items per sprint day.
  • Sprint length in calendar days.

4. Blocker Analysis

Section titled “4. Blocker Analysis”
  • Total flagged items during the sprint.
  • By assignee — who carried the most blockers, with the issue keys.

5. Team Contributions

Section titled “5. Team Contributions”
  • One row per assignee: total assigned, done, in progress, to do.
  • Sorted by Done descending.

6. Health Trend

Section titled “6. Health Trend”
  • A timeline of every hourly snapshot, with health score, total items, and done count.
  • This is what drives the Sprint Comparison view.

When autopsies generate

Section titled “When autopsies generate”
  • Automatically when a sprint moves to Closed — usually within minutes of the close.
  • The data persists in Forge SQL even if SyncUp is later uninstalled and reinstalled in the same site (subject to Atlassian’s retention policies).

Sending an autopsy as an email (admin)

Section titled “Sending an autopsy as an email (admin)”

Project admins can email the latest autopsy on demand:

  1. Settings → 🔔 Notifications
  2. Click the 🏁 Sprint Report button at the bottom of the notification settings.

The email is delivered through the same Jira-email channel used by the daily briefing (see Install → permissions for how that works).

Next

Section titled “Next”