How Can We Help?

1. Go to any Jira dashboard (or create a new one)
2. Click the Add gadget button
3. Search for "Project Commander"
4. Click Add to add it to your dashboard
5. Configure by selecting your board and setting capacity limits

This usually means no board is configured. Click the settings icon (gear) in the gadget and:

• Select your Scrum board from the dropdown
• Make sure your board has active or future sprints
• Verify you have permission to view the board

Only Scrum boards with sprints are supported.

Project Commander supports two estimation modes:

• Points Mode: Uses the Story Points field from your issues. Best for teams using relative estimation.
• Time Mode: Uses the time tracking field (hours or days). Best for teams tracking actual work time.

Choose your Estimation Mode in Settings. Both work with all features including auto-level and velocity tracking.

Auto-Level redistributes issues across sprints to balance capacity:

• Analyzes which sprints are over your configured limit
• Moves issues based on your chosen strategy: Priority, Size, Due Date, Balanced, or Compare All (runs every strategy and shows their delivery forecasts side-by-side)
• Respects issue dependencies (blockers stay in earlier sprints)
• Creates new sprints if needed (up to 10)
• Can use your actual velocity instead of manual limits

After Auto-Level runs, you'll see which issues were moved with color-coded badges. Click Undo to revert all changes, or Accept to save to Jira.

No. Every feature in Project Commander is available to every user — there's no premium tier, no per-feature upgrade prompt, and no behaviour change based on licence. Pricing applies to who pays, not what features they get. Pilot customers and Marketplace paid customers see the exact same app.

Yes! Each gadget instance is configured independently:

• Add multiple Project Commander gadgets to your dashboard
• Configure each one for a different board
• Each gadget maintains its own settings and velocity data

Project Commander tracks velocity when you complete sprints:

• Completed Points: Sum of points for issues in "Done" status when sprint closes
• Average Velocity: Mean of completed points across recent sprints
• Expected Velocity: Weighted prediction based on trends
• Efficiency: Completed points divided by sprint capacity

Configure how many sprints to include (1-20) in settings. The Settings panel offers presets of 3, 5, 8, or 10; the Dashboard allows any value from 1 to 20.

Yes. Project Commander is built on Atlassian Forge, which provides enterprise-grade security:

• No data is stored outside Atlassian's infrastructure
• All API calls go through Atlassian's secure gateway
• Your Jira data is never copied to external servers
• API keys are stored with encryption
• Access follows your existing Jira permissions

For the standalone web app, your credentials are stored only in your browser's session storage and cleared when you close the tab. They are never stored on our servers. The API proxy only forwards requests to *.atlassian.net domains.

See our Privacy Policy for details.

The standalone web app at projectcommander.app/app lets you try Project Commander with your own Jira data without installing anything. You connect using your Jira email and API token. It provides the same analysis as the Jira Cloud app — capacity planning, risk analysis, delivery forecasting — in read-only mode by default.

The standalone web app is currently in beta and requires an access code to connect your own Jira. Demo mode is always open without a code. To request a code, email support@projectcommander.app with your name and company. We'll send you a code typically within 24 hours.

Read-only mode (the default in the standalone app) means Project Commander reads your Jira data to generate analysis but does not create, modify, or delete any issues, sprints, or other Jira data. You can toggle read-only mode on/off using the button in the top banner.

In the standalone web app, your Jira credentials (email and API token) are stored in session storage and are automatically cleared when you close the browser tab. You'll need to re-enter them next time. Your beta access and app settings are preserved in local storage so you won't need to re-enter your beta code.

Every open risk carries a response strategy — your decision about how to handle the risk while it's open. Pick from:

• Avoid — remove the source by changing scope, schedule, or approach
• Mitigate — reduce probability or impact with concrete actions (default)
• Transfer — move the risk to a vendor or partner team (requires an Accountable owner)
• Accept — absorb the risk; requires a rationale
• Escalate — needs portfolio or leadership decision; surfaces in Alerts under "Escalated risks awaiting decision"
• Defer — not enough information yet; requires a future review-by date
• Undecided — initial value; prompts you to pick a strategy on next edit

The strategy chip shows under each risk title. The Dashboard's Top Open Risks widget summarises the mix and sorts Undecided / Escalate above Accept at the same severity so attention-demanding items surface first.

The Scope tab renders both on the same chart, so you can read whichever framing your team uses:

• Burndown view — Scope, Remaining, Ideal Burndown. Teams that track "work left" read these lines.
• Burnup view — Burnup, Ideal Burnup, Burnup Forecast. Teams that track "work completed" read these.

Both views come from the same data — every point burned down lifts the burnup line by the same amount.

You can connect Anthropic (Claude), OpenAI (ChatGPT), or Google (Gemini). Configure your provider and API key in Settings → AI Features. The key never leaves your browser; data is sent per-request directly to the provider you chose. AI features (Insights, risk narratives, chain analysis, sprint review) only run when triggered after a key is saved — there's no telemetry or background AI activity. Removing the key disables all AI features.

A short disclosure in Settings names exactly what sprint data gets sent to the provider when a key is configured: issue summaries, assignee names, sprint names, and story points. Nothing else.

Yes. Open the Projects tab and click + Add Project to register additional projects. Once two or more are registered, a "Program view" option appears in the header selector. Switch to it and every tab — Dashboard, Scope, Alerts, Risks, Actions, Epics, Team & Capacity, What-If — unions data across every project you manage. You can declare cross-project dependencies, allocate people across projects via the Team Allocation Matrix, and run inline what-if mutations (add headcount, shift scope, change target dates) with per-step Revert.