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

If you've configured a board, this usually means the board has no active or future sprints, or you lack permission to view it. Click the settings icon (gear) and:

• Pick a board from the dropdown
• Make sure the board has active or future sprints
• Verify you have permission to view the board

If you're running a Kanban or ad-hoc workflow with no sprints, switch off Sprint Mode in Settings and use a JQL filter instead — every tab (Dashboard, Scope, Alerts, Risks, Actions, Team & Capacity, What-If, Projects) works in the sprintless mode too.

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. Beta users and post-beta paid customers see the exact same app.

Yes — two ways, depending on what you're after:

• Multiple independent gadgets on one dashboard. Add several Project Commander gadgets, configure each one for a different board, and each one keeps its own settings and velocity data. Best when you want side-by-side views of unrelated boards.
• Register the boards as projects in a Program. Open the Projects tab → + Add Project for each board you want to track, then switch to Program view in the header selector. Every tab (Dashboard, Scope, Alerts, Risks, Actions, Epics, Team & Capacity, What-If) unions data across the projects, and you also get cross-project dependencies, shared team allocation, and program-wide what-if. See the "Can I run multiple projects as a program?" entry below for the full feature list.

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

See our Privacy Policy for details.

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 is held in Atlassian Forge's encrypted secret storage and is only read server-side when an AI call fires — the request goes from the Forge backend directly to the provider you chose, never through a Project Commander server. AI features only run when you explicitly trigger them after a key is saved; there's no telemetry or background AI activity. Removing the key disables every AI feature and is wiped on uninstall.

Current AI features: Dashboard Insights (inline on the Dashboard tab), AI Chat (in the What-If tab), AI Risk Suggestions, What-If Analysis, and Retrospective Summaries.

The prompt the provider receives includes: issue keys, summaries, statuses, story points, time estimates and time spent, priority, issue types, assignee display names, due/start/resolution dates, dependency links (blocks / blocked-by), epic links, sprint names, sprint states, sprint dates, sprint goals (free text), team-member display names, hours per week, utilization, average velocity, time-off entries (member name, dates, reason), holiday entries, and velocity history. For AI Chat, the message you typed is also included. The prompt does not include full issue descriptions, attachments, or issue comments. See the Privacy Policy §4 for details.

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.