Plan the work. Forecast the date.
Monitor what threatens it.

Know whether your Jira plan will deliver — before you commit to the date.

An add-on for Jira, not a replacement for it. Jira stays where the work lives; Project Commander reads it and tells you whether the plan holds. How it compares with Jira, Jira Premium and Rovo →

Try the live demo →

Sample Jira data. No signup, nothing to install — about 60 seconds.

Then connect your own Jira — read-only

Your real project, in the browser. Still nothing installed.

Built on Atlassian Forge• See it on the Atlassian Marketplace →
Project Commander Delivery forecast ▾
⚠ Likely 3 weeks late
Current forecast: Sep 24, 2026  ·  Target date: Sep 3, 2026
What to fix
Jul 27
Start Sep 3
Target Sep 24
Forecast
8 weeks +3 weeks
Demand vs. capacity ■ Within capacity  ━ Capacity  ■ Overload
Jul 27Aug 3Aug 10Aug 17Aug 24Aug 31Sep 7Sep 14Sep 21
Primary driver
Backend capacity
The backend team is over capacity from Sep 7 — planned work plus time off. That overload creates the three-week slip.
View capacity
Will we deliver on time?
Who's overloaded?
Where's scope creeping?
What needs fixing now?

Why Project Commander exists

It came from a recurring frustration: Jira tells you what's happening, but not whether the plan will actually land — so teams find out too late that a commitment wasn't realistic.

It is an add-on to Jira, never an alternative to it. It installs into your own Jira site, reads the projects, sprints, issues, people, time tracking and links you already keep there, and leaves Jira as the place the work lives. The only things it stands in for are the planning and capacity features of Jira Premium and the delivery reporting of Rovo.

Project Commander was built to answer that up front: can we deliver this in the time and capacity we have, and if not, where's the risk — and to make that answer something you can put straight in front of stakeholders. Every number is arithmetic on data already in Jira. More in the FAQ →

Read the whole answer on the FAQ · How it compares with Jira, Jira Premium and Rovo · and with Tempo Capacity Planner, Portfolio by HeroCoders, ActivityTimeline and Planyway

A Complete Toolkit — Plan, Forecast, Monitor

Built for project managers, scrum masters and engineering leads who are tired of saying "we'll see" when stakeholders want a real date.

Once the plan is sound, two things quietly break it: scope creeping in and capacity slipping out. The rest of the app watches both.

Plan
📋

Planning

Drag work between sprints, edit points, estimates, dates or assignee straight in the table, and let Auto-Level rebalance an overloaded plan in one click.

🔗

Dependency Tracking

See what blocks what, including loops and blockers scheduled after the work they hold up, with the conflicts flagged on the sprint they threaten.

🏙

Program Management

Run every project from one table, with capacity, forecast and alerts rolled up, and people split across projects counted once at their real share.

📅

Timeline Coming soon

A Gantt chart nobody has to maintain: every epic and issue drawn as a bar where the forecast puts it, with dependency arrows and the critical chain on the same picture.

Forecast
📅

Delivery Forecast

A finish date from the project’s own sprints, capacity and dependencies, with the gap to your target and the odds of hitting it stated plainly.

🔎

Impact Analysis

Move a slider for people, scope, pace or estimate accuracy and watch the date move — or run a Monte Carlo simulation for the odds instead of one date.

📊

Capacity × Demand grid

Every way of measuring capacity against every way of treating dependencies, in one grid, so you can see whether the answer holds however you look at it.

Monitor
🚨

Alerts

One list of what threatens the date: blocked work, dependency conflicts, missing estimates and dates, and overdue issues — dismiss one and it stays dismissed.

☑

Risks & Actions

A risk register with owners, probability, impact and mitigations, plus actions with due dates — both kept per project and carried between sprints.

🎯

Epic Tracking

Progress per epic against the capacity available to it, so you can see which epic is quietly consuming the sprint and which is on track.

See All Features with Screenshots

1 · Plan

Make the work fit the team you actually have.

Sprint 7 is overcommitted.
Sprint 8 is even worse.

Every sprint carries a Deliverable or Overcommitted badge, with the work it holds and the capacity it has on the same line. When one is overloaded and the next has room, Auto-Level rebalances them in one click — and shows you what it moved before anything is saved.

Stop manually dragging issues between sprints for an hour every Monday.

Sprints tab: the active Sprint 7 open and Overcommitted with its issue table, and the future Sprints 8, 9 and 10 closed, each showing demand, capacity, load and scope

Someone is underwater.
How much can your team take on?

Every person, their work and their capacity, side by side: who is overloaded, who has room, and by how much. Weekly hours, time off and company holidays all come out of the number, so an overcommitted sprint cannot hide behind a green team total — points under average velocity is not capacity planning.

Someone split across three projects only owes you their share of the week, and that share is what the capacity number uses.

Stop burning out your best people. Capacity planning that accounts for real life.

See how Jira capacity planning works →·Read your Jira team velocity properly →

Team & Capacity tab: per-member rows with weekly capacity, utilisation, the Alloc column showing percent totals per unit, time-off deductions, and status badges
2 · Forecast

Know whether the date still holds — and what changes it.

You committed to a date.
Is it still realistic?

Four cards answer it at a glance: are you on pace, what date the work now lands on, what date you promised, and how much is done. Underneath, the forecast is repeated for every way of measuring capacity and every way of treating dependencies, so you can see whether the answer holds up however you look at it — with the odds of hitting the target on each one.

No digging through boards, no guessing. Open the dashboard, get the answer.

Dashboard: the four stat cards — On Pace? (Ahead of pace, 255 pts completed against 211 planned), Delivery Forecast (Dec 15, 2026, not on target, 44 days late), Target Date (Nov 1, 2026), Progress (57%) — above the open Delivery Forecast grid, with capacity models (Each sprint's own setting, Effective team capacity, Team capacity, Velocity) as rows against demand models (Ignore dependencies, Respect dependencies, Resequence work, Critical Chain only) as columns, each cell a finish date, its gap to target and its on-target odds, shaded green, amber or red, with the Critical Chain floor flagged Earliest

See the impact before
you make the call.

Move a slider — more people, less scope, a team going slower — and the delivery date moves with it, showing which sprints absorb the overflow. Or run a Monte Carlo simulation and get odds instead of a single date: "85% chance by Sep 24" is a number worth putting in a status update.

What-If tab: velocity and scope sliders, cascade chart, Monte Carlo probability forecast
3 · Monitor

Catch what breaks the plan after you have made it.

Scope keeps growing.
Nobody sees it happening.

Scope history is rebuilt from Jira itself, so you can see what the plan started as, what it is now, and the day each piece arrived. When the finish date moves because work was added rather than because the team slowed down, this is where you prove it.

Scope creep is the silent project killer. Now it's visible.

How to track scope creep in Jira →

Scope tab: the weekly chart with three lines — Ideal Burndown, Remaining and Scope — the Scope line climbing from 30 points to 445 as work is added

Running multiple projects?
See them all in one place.

Every project in one table — forecast, health, how much slack is left, what is alerting. Switch to the program view and every tab answers for the whole portfolio instead of one project, including the people shared across several of them.

A critical chain diagram shows the resource-constrained path to delivery across all projects — which issue is blocking everything else, and who is the bottleneck.

Projects tab portfolio table: one row per project with health, progress, forecast, target, slack, scope, utilization, team, alerts, and estimation columns, and a Program rollup row at the bottom

A Gantt chart
nobody has to maintain. Coming soon

Every other Gantt draws a bar where somebody dragged it, and somebody has to keep dragging it for the picture to stay true. Here the bars sit where the forecast puts them — from the size of each job, who has it, the hours they really have, their time off, and what blocks what. Change an estimate, a person or a date and the whole chart redraws.

Built and in testing. Not in the released app yet — see what it does →

Timeline tab: the folding notice open, the work listed earliest due date first, dependency arrows between the bars, a six-days-late measurement, the allowance tail to the forecast pin, and the key along the bottom

See It in Action

Take the full product tour — Dashboard, Sprints, What-If, Team & Capacity, Scope, Alerts, and more.

Try the live demo →

Your Jira or demo data — no install, no sign-up.

Plan Better. Ship on Time.

Plan the work, forecast the date, and monitor what threatens it — from the demo, from your own project read-only, or installed for the whole team. Works with sprints, or without them from a filter, in story points or time estimates.

Get it on the Atlassian Marketplace Try the live demo →

Free during beta — no credit card, no commitment. Questions? support@projectcommander.app