If you run delivery on Jira, you know it's excellent at the "what" — what issues exist, who they're assigned to, what status they're in. What it doesn't tell you is whether the plan actually holds: will we finish on time, who's overloaded, and what happens if scope grows.
That gap is why we built Project Commander, and it's now live on the Atlassian Marketplace. I wanted to share the thinking behind it here, because it came out of problems this community talks about all the time.
Most Jira reporting looks backward — burndown, velocity, what already happened. The harder question is forward-looking: given the work on the books and the capacity we actually have, week by week, can we realistically deliver by the date we committed to?
Project Commander answers that by combining a project's demand (issues, estimates, dependencies) with its real capacity (people, weekly hours, time off, holidays) across time. That single comparison is what turns a board full of tickets into a feasibility call.
It's built entirely on Atlassian Forge, so your data stays inside Atlassian's cloud. It works with Jira Cloud, Scrum or hybrid, story points or time estimates, and runs as either a full-page app or a dashboard gadget. AI features are optional and user-controlled — the forecasting math is deterministic and auditable, not a black box.
I'd genuinely like feedback from people who plan delivery for a living. If you give it a try, tell me what's useful and what's missing — and if it helps, a review on the Marketplace goes a long way.
Get it: https://marketplace.atlassian.com/apps/3212730460
See it in action: https://www.projectcommander.app