Squad Portfolio · Live Snapshot

Compliance & Security — Portfolio Health

Active epics + story breakdown, deployment queue, and non-epic work · viewed as Product Manager · snapshot 25 Jun 2026 (refreshed)
Scope: Squad = "Compliance & Security" (cf[18750])
Epics (active) + child stories · plus all non-epic active tickets incl. Kzing Central

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

Done In progress To do Pending deployment Dropped (descoped)
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. Sub-tasks under in-scope stories are intentionally excluded. Click any epic to expand its stories.