Added-late bars
Which team got the most work added after the sprint started? Your changes stay on this page and never reach Jira. The sample is invented.
2. Map the columns
The page guessed these. Change one, and the bars follow.
3. Each team, sprint by sprint
The chart library did not load. Reload the page. The table below still holds the numbers.
What these numbers assume
- The export holds only the status of today. A ticket in 2 sprints counts as not done in the earlier sprint, and its status applies in the latest sprint.
- A label does not say which sprint it means. Added late counts in the first sprint of a ticket only, and the ticket counts as planned in its later sprints.
- Moving a person to another team also rewrites the past sprints of that person.
- Sprint names must match across teams, or the sprints do not line up.
4. Points per team, in one sprint
The number above each bar gives the points added late in stories and tasks. Bugs added late show in the muted orange and stay out of that number. Click a part of a bar to see and change its tickets.
The chart library did not load. Reload the page. The table below still holds the numbers.
| Team | Planned, done | Planned, not done | Added late: stories and tasks | Added late: bugs |
|---|
5. Curate the tickets
| Ticket | Summary | Type | Status | Points | Team | Added late | Counts | Why |
|---|
Save writes your mapping, your teams and your changes as text. Copy it somewhere. Next sprint, paste the new export, read it, paste this text here and press Load. The page matches tickets by issue key.