What the squad is betting on and why — a theme-grouped orientation layer over the same live Jira data in Portfolio health. Each bet shows its work-item status composition (raw counts, not a completion %) and owner concentration. Non-epic tickets are folded into their themes, so streams with no epic — like the Data & Reporting Foundation — are visible here for the first time. A non-epic ticket marked Done in Jira but with an empty Deployment Status stays in its bet, badged NOT DEPLOYED, until it is recorded as shipped or 30 days pass, so work does not disappear from the portfolio the day it is closed. Click a bet to expand its epics and tickets.
⠿ Drag a bet to reorder it within its tier; expand a bet and drag its epics to reorder those.
Needs your attention
Epic load by owner
Epics & story breakdown
Waiting on deployment — dev-complete but not confirmed live; "Done" with no Deployment Status is not shipped
Non-epic & unparented squad work — active squad tickets that don't roll up to any epic above, so the epic view can't see them
Static mockup built from a live Jira pull. Completion % is done ÷ active stories: Dropped/Cancelled tickets (which Jira files under the "Done" category) are split out, excluded from the count, and not treated as waiting on deployment. "Stale" = no child story updated in 14+ days, epic record also cold, and epic not yet complete. "Deploy queue" combines tickets in a Ready-for-Deployment status with tickets marked Done that have an empty Deployment Status field (cf[18751]). The Done-empty check is scoped to Story, Operation, Task and DB Request, the only types where that field is actually maintained; rows older than 30 days are more likely unfilled hygiene than a live queue. RDB and RLF tickets are treated as deployed once Resolved (those workflows have no separate deployment step), so they are excluded from this list. The non-epic panel covers Requests, Operations, Tasks, standalone Stories and other squad work that has no epic parent, including Kzing Central. Portfolio by theme additionally keeps non-epic tickets that are Done with an empty Deployment Status (Story, Operation, Task and DB Request only, resolved within 30 days) and badges them NOT DEPLOYED; the non-epic panel and its KPI on this tab stay scoped to open work, so those tickets appear once here, in the deploy queue. Sub-tasks under in-scope stories are intentionally excluded. Click any epic to expand its stories.