Reports¶
Reports turn Jira data into a health snapshot — progress bars, key numbers, a chart, risks and insights — and post it to Slack on your schedule. Choose Home → Explore reports in Slack, or build and preview them in the Workspace.
| Report | What it answers | Needs |
|---|---|---|
| Sprint health | Are we on track? Work done vs. time elapsed, burndown, blockers, stuck work, scope added mid-sprint, per-person progress. | A scrum project with an active sprint. Optional sprint name when a project has several boards. |
| Daily standup | Per person: finished since the last workday (Mondays include the weekend), in progress, and needs help. | Any project. |
| Epic progress | How is this epic doing? Completion, forecast finish date from the last 14 days of throughput vs. the due date, overdue/blocked/stale children, recent wins. | An epic key, e.g. PLAT-42. |
| Epics overview | Up to 40 open epics with progress and health, riskiest first. | Any project with epics. |
| Release progress | Is the next fix version going to make it? | A project; optional version name (defaults to the next unreleased version by date). |
| Team workload | Who is carrying what: open, in progress, overdue and stale per person, plus unassigned high-priority work. | Any project. |
| Weekly project health | Created vs. resolved over 6 weeks, backlog age buckets, overdue and the oldest open issues. | Any project. |
| Bug triage | New, unassigned and highest-priority bugs; fixed vs. reported this week. | Projects using the Bug issue type. |
| Velocity | Completed work across the last six closed sprints, with average and trend. | A scrum project with closed sprints. |
How numbers are calculated¶
- Story points or issue counts. If at least half the issues carry story points, reports use points; otherwise they count issues. The unit is always shown.
- Health. Sprints and releases with dates compare % work done with % time elapsed: within 10 points is On track, within 25 is At risk, otherwise Off track. Epics compare a forecast finish date with the epic due date.
- Forecast. Remaining work divided by the completion rate over the last 14 days. No completions in that window means no forecast (shown as No recent progress).
- Stale / stuck. No update for 3 days (in-progress sprint work), 7 days (epics, workload) or 2 days (standup).
- Scope added mid-sprint counts issues created after the sprint started. Issues moved in from the backlog are not detected.
- Change since last report. Scheduled reports compare headline numbers with the previous scheduled report, when one is available.
Options¶
- Skip when there is nothing to report — no empty posts.
- @mention people — names become Slack mentions once people are matched.
- AI insights — a short, clearly labelled AI summary on risks and next steps, guided by your own instructions.
- Refresh — every posted report has a Refresh button that rebuilds it in place with live data.
Charts
Chart images in Slack are drawn by QuickChart from numbers, dates and sprint names only — never issue titles. Turn them off under Home → Settings & help. The Workspace draws charts itself.
Charts in Slack¶
Reports use one chart where a visual helps: sprint burndown, epic and release progress, epic health counts, workload distribution, weekly created-versus-resolved trends, bug flow, and completed work across sprints. Standups keep their per-person action lists.
Images use the app’s blue palette, readable axes, and high-resolution PNG output. Numbers and issue links remain in the message if an image cannot load or chart images are switched off. Long trend images may sample dates evenly to fit Slack’s URL limit; the browser report retains the complete series.
Workload images group people by open-issue count. Individual names remain in the Slack text, rather than being sent to the external chart renderer. Progress and health images use aggregate counts; issue titles and people’s names are excluded from chart requests.