Frequently Asked Questions
How do I add Sprint Commander to my dashboard?
- Go to any Jira dashboard (or create a new one)
- Click the Add gadget button
- Search for "Sprint Commander"
- Click Add to add it to your dashboard
- Configure by selecting your board and setting capacity limits
Why don't I see any sprints?
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. Kanban boards don't have sprints.
What's the difference between Story Points and Time Estimates?
Sprint Commander supports two capacity metrics:
- Story Points: Uses the Story Points field from your issues. Best for teams using relative estimation.
- Remaining Estimate: Uses the time tracking field (hours or days). Best for teams tracking actual work time.
Choose your metric in the gadget settings. Both work with all features including auto-level and velocity tracking.
How does Auto-Level work?
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, or due date)
- 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
You'll see a preview of moves before confirming. This is a premium feature.
What happens when my trial ends?
When the free trial ends:
- Basic features continue to work (viewing sprints, drag-and-drop, velocity tracking)
- Premium features (Auto-Level) will prompt you to upgrade
- All your configuration and velocity data is preserved
- You can upgrade anytime through the Atlassian Marketplace
Can I use Sprint Commander with multiple boards?
Yes! Each gadget instance is configured independently:
- Add multiple Sprint Commander gadgets to your dashboard
- Configure each one for a different board
- Each gadget maintains its own settings and velocity data
How is velocity calculated?
Sprint 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-10) in settings.
Is my data secure?
Yes. Sprint 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.