Orders by team and state
Primary owner only. Click a team name or a segment to filter. Teams outside the nine JVM teams are shown as external-team.
Orders by topic and state
One topic per order. Click a topic or a segment to filter.
Team × topic
Counts of orders by primary owner and topic. Darker means more. Click a cell to filter.
Orders by sponsor
Who signs off the decision. Click a bar to filter.
Insights
Cross-cutting charts over the orders and assignments in view. The filter row still applies.
Priority vs effort
Each open order as a dot: effort (person-days) across, priority up. Big dots top-right are the big bets. ▲ marks At Risk. Click a dot to open the order.
Orders created per month
When orders entered the system, by their current state. Hover a segment for its orders; links open a filtered dashboard in a new tab.
Effort by topic and state
Sum of estimated person-days per topic, split by state. Closed orders carry no effort.
Teams per order
Distinct teams involved in each order. Zero means no internal assignment for the selected discipline.
Teams working together
All teams uses order ownership and participation. Dev / QA uses actual internal assignments, so the maps may differ. A cell selects orders shared by both teams.
How load is spread
People by number of orders they are on. A long tail on the right means a few people carry most orders.
Who carries each team's load
Share of the team's person-days on leads, developers and QA. A lead-heavy bar means fallback assignments or an overloaded lead.
Orders
Click a column header to sort, a row to open its details below. Dev / QA values are person-days; hover for the estimate basis.
Freeze dates & capacity
Allure test evidence
Import a mapped Allure snapshot to review manual-test effort, coverage gaps and reusable test projects. Live MCP connection is not configured. Imported evidence stays in this browser.
Order details
Who keeps the orders
Load from the assignments in view. ~person-days splits Dev and QA effort separately among the respective internal assignees (leads count as Dev). Closed orders carry zero days. Unstaffed effort is not assigned to people. orders counts distinct orders, including closed ones. Every roster member is listed.
Team load
Members assigned to orders in view. Click a team to filter.
Most loaded people
Top 15 by the selected measure. Click a person for their orders.