iskue

Features · Reports

Reports you can trust

Rename-proof burndown, velocity and a personal view of everything on your plate.

Reports here are computed live from your tickets' change history, not from snapshots that go stale. Every project gets burndown, velocity, sprint reports, cycle time, cumulative flow and workload views, plus a roadmap timeline of sprints and epics. A personal dashboard gathers your open work across every project you belong to — and when the default isn't enough, you build your own from gadgets.

9 report endpoints5 gadget types5 group-by dimensions4 CSV downloads

What you get

  • Rename-proof burndown — Sprint burndown replays recorded status changes and matches on status ids and DONE categories, so renaming a workflow status never corrupts the chart.
  • Honest velocity — Velocity counts story points per completed sprint — and because unfinished work returns to the backlog at completion, each bar shows what actually shipped.
  • Sprint roadmap timeline — Sprints render as bars on a shared time axis with a today marker and state colouring, with epic progress — done counts, points, due dates — underneath.
  • Cross-project dashboard — One view aggregates your open assigned tickets across every project you belong to, split by status category and by project, highest priority first.
  • Build-your-own dashboards — Compose dashboards from five gadget types — assigned to me, filter results, statistics, sprint burndown and notes — keep them private or share with all users, and set one as your default.
  • Flow metrics included — Cycle and lead time with a control chart, weekly throughput, cumulative flow, created vs resolved and per-assignee workload — four of them export straight to CSV.

See it

Burndown — Sprint 14
34170Day 1Day 10
Velocity — last 5 sprints
S10S11S12S13S14

History, not snapshots

Most trackers store a single resolution date and hope it stays accurate. These reports replay the ticket change log instead: a ticket counts as done from its last entry into a DONE-category status, so work that gets reopened and redone lands on the right day, and renamed statuses keep their history. Burndown, cycle time, cumulative flow and created vs resolved all share this derivation.

Dashboards reuse what you already trust

Gadgets do not run a separate aggregation engine. The filter-results and statistics gadgets execute a saved filter or a TQL query; the burndown gadget calls the same report as the project page; every gadget inherits your project visibility. A misconfigured gadget shows its own error instead of taking the whole dashboard down.

Bounded by design

Report queries are capped so pages render fast on large projects: flow metrics cover the 100 most recently finished tickets, cumulative flow and created vs resolved scan up to 500 tickets, and a statistics gadget groups up to 1,000 matches. The personal dashboard lists your top 50 open tickets, sorted by priority and recency.

In practice

GET /api/v1/projects/{projectKey}/sprints/{sprintId}/burndown
GET /api/v1/projects/{projectKey}/velocity
GET /api/v1/projects/{projectKey}/cycle-time
GET /api/v1/projects/{projectKey}/cumulative-flow

See Iskue on your own screen

A demo takes half an hour. A pilot runs on your servers, with your data, from day one.

Request a demoRead the FAQ