Concepts
What a blocker, a signal, a reason and a resolution mean in Impediment Ledger.
Impediment Ledger tracks the blocked periods behind Jira's native Flagged marker and records, for each, why work was blocked, who is resolving it and what resolved it. The flag stays in Jira; the app does not replace your board.
Terms
| Term | Meaning |
|---|---|
| Blocker (episode) | The period from flagging an issue until the flag is removed (or, when your admin chose them, while it is in a blocked status or blocked by an open issue). An issue has at most one open blocker at a time; time held by two signals at once counts once. |
| Signal | What marks an issue blocked: the flag (always), a status your admin chose (for example "Blocked"), or a link such as "is blocked by" to an issue that is not done. |
| Reason (category) | Why work is blocked (for example Environment, Decision pending). Counted as internal or external in reports. |
| Reason missing | The blocker has no reason yet. The "Reason missing" list lets you add it quickly. |
| Not a blocker | A built-in reason: the flag does not mean blocked here (for example a reminder). The flag stays in Jira; reports leave it out. |
| Resolution | What resolved the blocker. It can be written in advance and is confirmed when the flag is removed. |