-
⏱
Hours are worklog-based
This dashboard reflects time logged in JIRA worklogs. Unlogged work or entries back-dated outside the filter window will not appear.
-
✏️
Roadmap Mapping is a manual field
Orphan status is determined by whether the "Roadmap Mapping" field on a worklog row matches a known JIRA Initiative Key. Typos, abbreviations, or missing entries cause false orphans — these are data quality issues, not necessarily unplanned work.
-
📐
Orphan % is row-level, not issue-level
A single issue logged across multiple people/weeks counts as multiple rows. Orphan % reflects share of hours, not unique JIRA issues.
-
🔄
Data refreshes once weekly
The Actuals sheet refreshes midday Wednesday. Edits made after the Wednesday pull won't appear until the following week's refresh.
-
🏛
Initiative list is the source of truth
The Initiative tab (JIRA Key column) defines what is considered "linked." If a valid initiative is missing from that tab, hours against it will appear orphaned.
-
🏢
Org hierarchy completeness varies
L6 and Direct Manager fields may be blank for some resources depending on how the org is structured in the source system. Blank managers are grouped separately.
-
💡
Goal is directional, not a hard SLA
The 5% threshold is a PMO hygiene target. Bursts above 5% during roadmap re-planning or org changes are expected; sustained overages warrant clean-up.