Features

Every tab, every tool — what it does and why it matters.

🛠

Dashboard

  • Open the Dashboard tab for 4 stat cards: On Pace?, Delivery Forecast, Target Date, and Progress — each answering a key project question at a glance
  • On Pace? compares completed work to work due by today and shows the verdict (Ahead of pace / On pace / Behind pace) plus the delta — color-coded green / amber / red so plan health is obvious instantly
  • Delivery Forecast shows the projected date, the gap vs the last sprint (e.g. Beyond Sprint 10 (+4w)), remaining work, capacity to target, and the deliverability verdict
  • Gear icon on each card for per-card settings — choose forecast method, target source (latest due / latest sprint end / fixed), and pace measure independently
  • Diagnostics table with one-line factors covering Scope, Team Capacity, Delivery Rate, Estimate Accuracy, Team Balance, Dependency Conflicts, and Alerts — each row has tooltips and expand-for-detail
  • Widgets below the cards: Team Health Trend (rolling four-dimension health rollup), Top Open Risks (highest-severity unresolved risks), and Velocity History (recent sprint velocity bar chart)
  • Plan Quality Warnings banner for overloaded resources, dependency conflicts, and external dates at risk — each links to the relevant tab
  • Project AI chat panel — ask natural-language questions and get answers in three layers (headline, brief explanation, supporting numbers). Requires an API key
  • Weekly Digest one-page summary and full PDF export
Dashboard: 4 stat cards with delivery forecast, target date, progress, and diagnostics table
📋

Sprints

  • The Sprints tab lets you move issues between sprints with drag-and-drop — one at a time or select multiple with checkboxes to move in bulk
  • Toggle List View to see every issue across all sprints in a single sortable, searchable table — ideal for bulk review without opening individual sprint rows
  • Two-button mode selector per sprint: Sprint (default) and a state-aware second button — future and active sprints show Status (live progress), closed sprints show Retro (final retrospective)
  • Risks button in every sprint header opens a Risks modal scoped to that sprint with AI-detected risk factors (probability + impact + suggested mitigations) ready to accept
  • Inline editing in the issue table: click to edit Story Points, Original Estimate, Due Date, Assignee, Priority, or Summary — Enter to save, Escape to cancel. Zero-valued cells stay reliably clickable
  • Returning from a Jira link auto-refreshes sprint, project, and JQL data so edits made in Jira show up immediately
  • Quick-filter search inside any sprint card filters the issue table by key, summary, assignee, or status
  • JQL search box in the toolbar runs an ad-hoc Jira query and pulls matching issues into the view
  • Inline Create issue popover (project + type + summary) adds new issues to the backlog without leaving the tab
  • Load closed sprints on demand via the toolbar chip (Hidden / Last 5 / Last 20 / All) and run retrospectives on any past sprint
  • Every sprint shows a Deliverable, Tight, or Overcommitted badge plus demand vs capacity at a glance
  • See who's overloaded and who has room — click avatar chips in Demand by User to filter by person, expand for demand vs capacity bars
  • Auto-Level: split-button picker redistributes work across sprints using your chosen strategy (Priority, Size, Due Date, or Balanced — Balanced is the smart default that spreads load per assignee). A horizon picker limits how many sprints are rearranged (Next sprint / Next 2 / Next 3 / All); sprints beyond the horizon stay untouched. Each move shows a tooltip explaining why it happened (capacity, dependency, due date, lock, or horizon), and a summary panel above the board breaks down the deviations by reason. Compare All view, P50 / P85 forecast dates, skill-mismatch warnings, and optional one-click AI Review.
  • Velocity panel inline in the toolbar: sprint history, KPI tiles, and import controls, with effective-capacity efficiency per sprint
  • Sort by any column; drag to reorder issues within a sprint — custom order persists
  • Full sprint lifecycle: create, start, complete (with action-item and risk roll-over prompts), delete
Sprints: All sprints with deliverability badges, demand vs capacity, and Auto-Level

Auto-Level in Action

Watch Auto-Level redistribute work across sprints with one click — then undo or accept the result.

🎯

Epics

  • The Epics tab provides a single unified overview table — all epics in one sortable, searchable view
  • Progress bars, point totals, assignee, start/due dates, and Jira status fetched directly from the backend
  • Sortable columns, search, and dynamic status filter to find what you need fast
  • Scope change tracking per epic — see what was added since the baseline
  • Expandable rows to see child issues with their details
Epics: unified overview table with progress bars, point totals, assignee, dates, and expandable rows
🎲

What-If

  • The What-If tab has 4 distinct sliders: Velocity, Issue Estimation, Scope, and Capacity — each directly affects your projected delivery date in real time
  • Per-user stacked cascade chart with cross-hatch overflow to visualize who is over capacity and when
  • Direct connection to delivery forecast — sliders update the projected completion date instantly
  • Monte Carlo simulation with S-curve probability distribution for data-driven stakeholder forecasts
  • Sprint vs Project view toggle — sprint-based or weekly time-based analysis
  • Cascade overflow checkbox to control overflow visualization
What-If: 4 sliders and cascade chart showing capacity vs demand across sprints

What-If & Monte Carlo Video

Watch how changes to velocity, estimation, scope, and capacity affect your delivery date — then see a Monte Carlo simulation in action.

👥

Team & Capacity

  • Three collapsible sections: Team Members, Time Off, and Company Holidays
  • Per-member status badges: OPTIMAL, OVERLOADED, AVAILABLE, UNDERLOADED — see team balance at a glance
  • Add team members through an in-app + Add Member modal; existing members are also picked up automatically when you assign issues to them in your sprints
  • Configure each member's weekly hours, utilization %, and time off — capacity updates everywhere automatically
  • Period selector (Weekly, Biweekly, Monthly, Quarterly, Yearly) plus a Populate weeks button to bulk-fill capacity at the current rate
  • Show total / Show per selected project toggle: switch between aggregated capacity and project-scaled rows so the numbers reflect what each member has dedicated to one project
  • Alloc column on every row: each member shows Hrs: X% / 100% and Pts: Y% / 100% across the program's projects (red when over). Click the cell to open a popover with per-project percent inputs paired with an editable “= X pts/hrs” computed value — edit either, the other follows. Σ chips at the bottom of the popover sum the percents per unit and flag over-allocation independently for hours and points
  • Percent allocations survive capacity changes: bump a member's Pts/Wk or Hrs/Wk and every “= X” display in their popover recomputes from the new capacity without re-entering the allocations — a 60% allocation stays 60% across capacity changes
  • Click dates on the calendar to mark PTO; Ctrl+click toggles individual days, Shift+click selects a range. Add company holidays with optional recurring flag
  • Capacity data feeds Dashboard forecasts, What-If scenarios, and sprint planning simultaneously — one source of truth
  • The Demand vs Capacity chart now lives on the Scope tab, sitting next to the scope timeline that shares its data
Team & Capacity: per-member rows with weekly capacity, utilisation, the new Alloc column showing percent totals per unit, time-off deductions, demand, and status badges
📈

Scope

  • The Scope tab rebuilds changelog-based scope history from Jira issue changelogs — accurate, auditable tracking of exactly when and how scope grew
  • Stat cards across the top: Burned & Remaining, Scope on start, Scope now, change %, Start date (Fixed / Earliest start / Earliest due / Earliest sprint start), Target date (Fixed / Latest due / Latest sprint end), Delivery Forecast, and Capacity to target
  • Burndown and burnup on the same chart: Scope, Remaining, Ideal Burndown, plus Burnup, Ideal Burnup, and Burnup Forecast. Teams that report progress as work completed read the burnup; teams that report it as work remaining read the burndown — both views agree because they come from the same data
  • Forecast strategy picker (Priority / Size / Due Date / Balanced) decides what order to burn down; the separate Delivery Forecast Method picker (Sprint capacity / Effective capacity / Team capacity / Velocity) decides how fast. Compare All overlays every strategy on the same chart
  • Confidence band around the forecast trace: Off, Historical variability (width comes from your team's own velocity, scope-change, and estimate-vs-actual stddevs), or Monte Carlo (P10–P85 from ~600 simulation runs)
  • Per-user filter chips, Sprint Markers toggle, Include Backlog toggle, and period grouping: All Time, Weekly, Biweekly, Monthly, Quarterly, Yearly, or Sprint (buckets by the project's actual sprint windows)
  • Scope growth rate modeling — Average over period or Manual rate — factors in how fast scope is expanding for realistic forecasts
  • Demand vs. Capacity chart (collapsible) below the timeline: period capacity vs period demand over time, sharing the same target and projected-completion markers as the Scope chart
  • Weekly Breakdown table (collapsible): one row per period with Issues, Added, Burned, and cumulative Completed — expand any row to drill into the issues that contributed in that window
Scope: chart with Scope, Remaining, Ideal Burndown, Forecast plus Burnup, Ideal Burnup, and Burnup Forecast traces
🚨

Alerts

  • The Alerts tab finds every issue that needs attention and groups them by domain
  • Collapsible domain groups: Risk strategy (Escalated risks awaiting decision, Risk review due), Dependency risk (circular dependencies, blocker conflicts including an overdue-blocker check, child-after-parent), and Data quality (missing dates, missing estimates, done with remaining work). Each group shows its active count
  • Detects circular dependencies and cross-sprint conflicts automatically — circular cycles include an inline recovery hint naming the exact edge to break first
  • Dependency conflicts include an overdue-blocker check: fires when the blocked issue's start date has passed but the blocker is still open
  • Severity filter pills (All / Errors / Warnings) plus a search box that filters by issue key or any text in the alert message
  • Per-alert dismiss (the small × on each row hides it) with a Show dismissed (N) link to bring them back — dismissals persist locally
  • Create risk button next to each alert opens the Risks tab with a new-risk form pre-filled (probability, impact, source category) so a recurring alert becomes a tracked risk in two clicks
  • Badge count on the tab shows total alerts without opening the panel; click any alert to jump straight to the issue in Jira
Alerts: domain-grouped alert list with severity filter, dismiss controls, and create-risk shortcut
☑

Actions & Risks

  • The Actions tab tracks follow-through items raised during sprint reviews, retrospectives, planning, or alert triage. Cards render with a left-edge severity stripe so high-priority work stands out
  • Action fields: title, description, owner, originator (defaults to your name), priority, scope (program / project / sprint), status, optional links to related risks
  • Filter by status, scope, originator, or assignee; sort by date opened or priority. Mark done and Reopen buttons handle premature closures cleanly. Dated comments form a running log per action
  • The Complete Sprint dialog walks each open action and prompts you to mark it done, roll it over, or close it — nothing falls through the cracks
  • The Risks tab is split into AI Generated suggestions (auto-detected from your sprint data) and Manually Entered risks (the formal register). Detectors raise items like velocity drops, scope creep mid-sprint, single-point-of-failure resourcing, and cross-sprint dependency conflicts
  • Each risk has Probability (1–5) × Impact (1–5) with derived Severity, RACI owners (Accountable, Responsible, Consulted, Informed), Originator, and lifecycle status (Open / Mitigated / Accepted / Closed)
  • Response strategy on every risk — pick from Avoid, Mitigate, Transfer, Accept, Escalate, Defer (or leave Undecided). Strategy-specific required fields (escalation owner, review-by date, rationale) plus a full audit trail of strategy changes
  • Accept dialog includes detector-specific mitigation suggestions plus an AI narrative layer (when an API key is configured). Accept moves a suggestion into Manually Entered with a full audit trail
  • Filters: Source (All / Manual / AI), Status, Strategy (All / Undecided / Avoid / Mitigate / Transfer / Accept / Escalate / Defer), Scope (All / Program / Project / Sprint). On-tab toggles: AI risk suggestions and Auto-close risks when all mitigation actions complete
  • The Dashboard's Top Open Risks widget adds a strategy mix bar (e.g. "4 mitigate · 2 accept · 1 escalate · 3 undecided") and sorts Undecided and Escalate risks above Accept at the same severity, so attention-demanding items surface first
  • The Complete Sprint dialog lists every risk whose linked actions are all complete and offers one-click Mark Closed — the register stays current without manual cleanup
  • Badge counts on both tabs show open items at a glance
Actions tab: action cards with severity stripe, owner, priority, status, and comment log Risks tab: AI-generated and manual risk register with probability, impact, severity, and RACI owners
🏙

Projects

  • The Projects tab shows every project's Health (Healthy / At Risk / Critical), Progress %, Forecast date, Target date, Slack days, Scope, Utilization, Team size, Alert counts, and Estimation coverage in a single table — everything visible without drilling in
  • A Program totals row at the bottom rolls weighted averages across every registered project
  • Switch the header selector to Program view and every tab — Dashboard, Scope, Alerts, Risks, Actions, Epics, Team & Capacity, What-If — unions data across every project you manage
  • Inline what-if mutations at program level: type a new scope value, pick a new target date, or click +/− on Team to add or remove headcount — the row shows before → after with a plain-language explanation. Hit × Revert next to any pending change to undo just that step
  • + Add Project requires Project Key, Board ID, and a JQL Filter; Edit and Delete buttons sit on every row, with confirmation before delete
  • Team Allocation Matrix (collapsible): a grid of every team member × every project. Each cell stores the percent of capacity dedicated to the project, shown as a percent input plus an editable “= X pts/hrs” computed line — edit either, the other follows. Hours and points percents are independent. Status column shows Σ per-unit totals against 100% and flags over-allocation per unit independently. Capacity changes (Pts/Wk, Hrs/Wk) update every “= X” display live without re-entering allocations. Setting a cell to zero when the member still has unfinished work prompts for confirmation
  • Critical Chain (collapsible) calculates the resource-constrained sequence that drives the earliest possible finish date — dependencies plus the fact that the same person cannot be in two places at once
  • Cross-Project Dependencies (collapsible) lets you declare that one project blocks another. Upstream slips past a downstream target date trigger a violation flag
Projects tab: multi-project table with health, forecast, slack, utilization, and alerts per project

Ready to Take Command?

Try It Free — Demo or Connect Your Jira →

Free during beta — no credit card, no commitment. Your credentials stay in your browser. Questions? support@projectcommander.app