Commitment Tracker for Jira

About and how it works · Support · Privacy policy · Terms

Pick a Jira release or a set of epics and compare it with any past date. Commitment Tracker rebuilds the past from Jira's own change history and shows what slipped, what was added or removed, what got done and what is newly blocked.

Get started

1. Install it from the Atlassian Marketplace. Nothing to set up.
2. Open any project and choose the Commitment Tracker tab.
3. Pick A release or A set of epics.
4. Choose what to compare with: 1, 2 or 4 weeks ago, or a checkpoint you saved.

The three tabs

• Timeline: each feature (epic) on a week grid at its target date, with how far it moved, its progress and blocked work.
• Changes: everything added, removed, slipped, completed or newly blocked, in week columns.
• Attention: work that is blocked now, overdue, or has no date.

Click anything to see the issues behind it, how it was worked out, and a Copy JQL button.

Checkpoints

Jira doesn't keep a history of release dates. So the first time you open a scope each day, the app saves a private checkpoint. From your second visit, release slip is measured in days. You can also save a named checkpoint from the ⋯ menu, for example before a steering meeting. Checkpoints are visible only to you.

Colours

Green: on track or done. Orange: slipped. Red: slipped more than two weeks, or newly blocked.

Limits

• Up to 2,000 issues per release or set of epics.
• Target dates come from the Due date field by default; a Jira admin can choose another date field in the app's settings (Jira settings → Apps).