Ownership Gap Detector(2.5.7)

An unowned ticket in the backlog is an inconvenience. An unowned ticket that is marked In Progress records work in flight with no one assigned to it, so the event stream carries no owner for whatever happens to it next. This visual shows you the full picture of ownership gaps across your projects, broken down by workflow status.

Unowned In Progress issues have no assignee on record. Whether that matters depends on your own way of working and your own control framework; the events show the gap, not its consequence.

What you can conclude

• An unowned In Progress issue is work in flight with no assignee on record; a reviewer could ask who is working on it.
• A large number of unowned To Do issues means issues are being created without being assigned.
• An ownership gap that grows over time means issues are reaching this state faster than they are being assigned.

How this chart works

Grouped horizontal bar chart showing the count of open unowned issues per project, broken down by current workflow status. Two kinds are counted together: tickets never assigned to anyone (typically fresh intake that was never triaged) and tickets whose assignee was later removed. The underlying data keeps them apart, so a project whose gap is entirely never-assigned is an intake question, while one carrying removed assignees is a handoff question. Each bar represents a combination of project and status. Statuses are identified by their Jira status id, so a status that was renamed or is shown in another language stays one bar, labeled with its most recent name; a ticket whose latest event carries no status takes its status from the most recent event that records one, including a status change Jira recorded only in that event's change history.

A ticket counts as open when that latest recorded status is in Jira's To Do or In Progress category. Each ticket counts once, under its current project, even when it moved between projects; deleted tickets, tickets in a project moved to the trash or deleted and not restored, and tickets whose events record no status that maps to a Jira status category are not counted.

Use the project filter to focus on a specific team. The date range does not apply to this visual: it counts the issues that are unowned right now, so every bar describes the present rather than a window.