Choose your capacity metric (Story Points or Remaining Estimate)
Click Save Configuration
3. Configuration
Access settings by clicking the gadget's edit button (pencil icon) on your dashboard.
Board Selection
You can configure your board in two ways:
Enter Board ID manually - Type the board ID directly if you know it
Select from dropdown - Click "Or select from available boards" to browse all boards you have access to. Select a board by name and the ID is filled in automatically.
Settings Reference
Setting
Description
Board ID
The ID of your Jira board (required). Can be entered manually or selected from a dropdown.
Capacity Metric
Choose between Story Points or Remaining Estimate (time)
Time Unit
When using Remaining Estimate, display as Hours or Days
Capacity Mode
Track capacity Per Sprint (total) or Per User (individual)
Capacity Limit
Default capacity limit for sprints or users
Progress Indicator
Show work remaining as a percentage in sprint headers (None, Remaining/Original, or Work Ratio)
Sprint Length
Duration for auto-created sprints (2, 3, or 4 weeks)
Display Columns
Select which columns appear in issue tables (Key, Summary, Assignee, Points, Status, Type, Priority, Start, Due)
Start and Due Date Columns
You can enable optional columns to display issue start dates and due dates:
Open gadget settings (Configure)
In the Display Columns section, enable Start and/or Due
Save the configuration
Date column features:
Format - Dates display as "Mon DD" (e.g., "Jan 14")
Past-due highlighting - Due dates in the past are shown in red bold text
Empty dates - Issues without dates show a dash (-)
Disabled by default - These columns are off by default to keep the view clean
Tip
Enable the Due column to quickly spot overdue items. The red highlighting makes past-due issues immediately visible.
4. Sprint View
The main view shows all active and future sprints from your board, plus the backlog.
Sprint Card Elements
Sprint State Badge - Shows ACTIVE or FUTURE status
Collapse/Expand Arrow - Click to show/hide sprint details
Reorder Buttons - Move sprints up or down in the display
Capacity Limit - Click to set a custom limit for this sprint
Date Range - Click to edit sprint start and end dates
Sprint Goal - Click to add or edit the sprint goal inline
Progress Indicator - Shows percentage of work remaining (when configured)
User Chips - Shows points per assignee; click to filter, double-click to edit capacity
Issues Table - List of issues in the sprint (scrollable when more than 10 issues)
Sprint Goals
Each sprint can have a goal that describes the sprint's objective. Goals are editable inline:
View goal - The goal displays below the sprint dates as "Goal: [text]"
Add goal - Sprints without goals show "Click to add goal"
Edit goal - Click on the goal text to open an inline editor
Save changes - Click Save to persist the new goal
Cancel editing - Click Cancel to discard changes
Clear goal - Save with empty text to remove the goal
Sprint Actions
Start Sprint - Available for future sprints with dates set
Complete - Available for active sprints
Sync Dates - Sync issue dates to sprint dates
Delete - Available for future sprints (with or without issues)
5. Capacity Planning
Sprint Commander provides visual warnings when capacity limits are exceeded.
Per Sprint Mode
In this mode, the total points/hours for all issues in a sprint are compared against the sprint limit.
Sprints over capacity show a red border and warning banner
The progress bar turns red when over limit
Click "Capacity Limit: X pts" to set a custom limit for individual sprints
Per User Mode
In this mode, each team member's workload is tracked against individual limits.
User chips show points and limit (e.g., "John: 15/20")
Users over capacity are highlighted with a warning icon
Click any user chip to set a custom capacity for that user in that sprint
Custom limits show with an asterisk (*)
Tip
Per-user limits are stored per sprint. You can set different limits for the same user across different sprints (e.g., if someone is on vacation).
Oversized Issue Warnings
When an individual issue exceeds the sprint capacity limit, it displays a warning:
A yellow warning icon (⚠) appears next to the issue's points/hours
The points value is displayed in red
Hover over the warning to see a tooltip explaining the issue
Oversized issues cannot fit within a single sprint's capacity. Consider:
Breaking the issue into smaller subtasks
Increasing the sprint capacity limit
Accepting that this sprint will be over capacity
Note
When using Auto-Level, oversized issues are distributed across sprints (one per sprint) rather than all staying in the same sprint.
Progress Indicator
The progress indicator shows the percentage of work remaining in each sprint, displayed next to the capacity in the sprint header.
Configuration Options
Option
Formula
Best For
None
—
Hide the progress indicator
Remaining / Original
Remaining Estimate ÷ Original Estimate × 100
Tracking progress against original scope
Work Ratio
Remaining ÷ (Time Spent + Remaining) × 100
Tracking actual completion including logged work
Tip
The progress indicator requires issues to have time estimates in Jira (Original Estimate field). Sprints without estimated issues won't display the indicator.
6. Auto-Level
Auto-Level uses an intelligent algorithm to redistribute issues while respecting dependencies, due dates, and capacity limits. It works in both sprint mode and per-user mode.
How It Works
Click the Auto-Level button (only enabled when sprints/users are over capacity)
Choose your strategy for selecting which issues to move
Click Auto-Level to proceed
The algorithm analyzes dependencies, dates, and capacity
Issues are redistributed to stay under capacity limits
In sprint mode, new sprints are created if needed (up to 10)
A summary shows how many issues were moved, with any date warnings
Strategy Selector
Choose how the algorithm selects which issues to move first:
Priority (default) - Moves lowest priority issues first. High priority work stays in earlier sprints.
Size - Moves largest issues first. Frees up the most capacity with fewer moves.
Due Date - Moves issues without urgent deadlines first. Keeps time-sensitive work in place.
Date-Aware Placement
When finding a target sprint for an issue, the algorithm:
Prefers sprints that fit - Sprints where the end date is before the issue's due date are ranked higher.
Shows warnings - If an issue must be moved to a sprint that doesn't fit its due date, a warning is displayed.
Never blocks moves - Date constraints are soft warnings, not hard blocks. The algorithm will still move issues when needed.
Smart Algorithm
The Auto-Level feature uses a sophisticated algorithm that:
Respects dependencies - Issues are never placed before their blockers. If Issue A is blocked by Issue B, A is guaranteed to be in the same sprint as B or later.
Detects cycles - If circular dependencies exist (A blocks B, B blocks C, C blocks A), Auto-Level will warn you and cannot proceed.
Preserves original positions - Issues stay in their current sprint unless they need to move to meet capacity limits.
Distributes oversized issues - Issues larger than the sprint capacity are distributed across sprints rather than stacking up in one sprint.
Per-User Mode
When capacity mode is set to "Per User", Auto-Level balances each user's workload:
Identifies users over their capacity limit in each sprint
Moves their excess issues to sprints where they have room
For empty sprints (no issues yet), uses the sprint capacity limit instead
Respects dependencies in user mode too
Auto-Level Rules
Dependencies are analyzed using topological sorting (Kahn's algorithm)
Issues move to later sprints only when necessary
New sprints are created with sequential dates based on your sprint length setting
The process respects individual sprint capacity limits
Tip
If Auto-Level reports a dependency cycle, use the dependency warnings in the sprint view to identify which issues are involved. Break the cycle by removing one of the blocking relationships in Jira.
7. Dependency Warnings
Sprint Commander warns you when issue dependencies create scheduling conflicts.
What It Detects
A dependency violation occurs when:
Issue A is blocked by Issue B
But Issue B is scheduled in a later sprint than Issue A
This means you're planning to work on a blocked issue before its blocker is complete.
Visual Indicators
Issues with violations show an orange warning icon (⚠) next to the issue key
Hover over the warning to see which blocker is in a later sprint
The header shows a count of blocked issues
Affected rows are highlighted with an orange background
Resolving Violations
To fix a dependency violation, either:
Move the blocker to an earlier sprint (same as or before the blocked issue)
Move the blocked issue to a later sprint (same as or after its blocker)
8. Drag and Drop
Move issues between sprints by dragging and dropping. You can move single issues or select multiple issues for batch moves.
Moving a Single Issue
Click and hold on any issue row
Drag towards another sprint
The page auto-scrolls when you drag near the top or bottom edge (within 100 pixels)
Drop the issue on the target sprint (highlighted with a blue border)
The issue moves immediately (optimistic UI update)
Multi-Select Drag and Drop
Move multiple issues at once using the checkbox selection:
Use the checkboxes in the first column to select issues
Select issues from one or more sprints
A selection indicator shows how many issues are selected
Drag any selected issue to move all selected issues together
Drop on the target sprint - all selected issues move as a batch
Selection is cleared after a successful drop
Selection Tips
Use the checkbox in the sprint header to select/deselect all issues in that sprint
Click Clear Selection in the header to deselect all issues
The selection indicator shows the count and total points of selected issues
Auto-Scroll Feature
When dragging issues, the page automatically scrolls to help you reach distant sprints:
Scroll down - Drag to the bottom edge of the viewport
Scroll up - Drag to the top edge of the viewport
Scroll speed increases as you get closer to the edge
Release the mouse to stop scrolling
Moving to Backlog
Drag an issue (or selected issues) to the Backlog section at the bottom
If the backlog is empty, a drop zone appears when dragging
Issues are removed from sprints and returned to the backlog
Tip
Use multi-select to quickly rebalance work between sprints. Select all over-capacity issues and drag them to a future sprint in one action.
9. Date Synchronization
Keep issue dates aligned with sprint dates for accurate roadmaps and reports.
Sync Dates for a Sprint
Ensure the sprint has start and end dates set
Click Sync Dates on the sprint card
All issues in the sprint will have their:
Start Date set to the sprint's start date
Due Date set to the sprint's end date
Sync All Dates
Click Sync All Dates in the header
This syncs dates for all sprints that have dates configured
Remove All Dates
Click Remove All Dates to clear start/due dates from all issues
A confirmation dialog prevents accidental removal
10. Sprint Management
Creating a Sprint
Click + Create Sprint
Enter the sprint name (required)
Optionally set start and end dates
Optionally add a sprint goal
Click Create Sprint
Editing Sprint Goals
Click on the goal text (or "Click to add goal" for sprints without a goal)
Edit the text in the input field
Click Save to apply changes, or Cancel to discard
Editing Sprint Dates
Click on the date range text (e.g., "Jan 13 - Jan 27")
Use the date pickers to adjust dates
Click Save
Starting a Sprint
Only future sprints with dates can be started
Click Start Sprint
Confirm the action
The sprint becomes active
Completing a Sprint
Only active sprints can be completed
Click Complete
Confirm the action
The sprint is closed and removed from view
Deleting a Sprint
Only future sprints can be deleted (not active or completed sprints)
Click Delete on the sprint card
If the sprint has issues, a dialog will ask where to move them:
Move to Backlog - Issues are returned to the backlog
Move to another sprint - Select a destination sprint from the dropdown
Click Delete Sprint to confirm
Issues are moved first, then the sprint is deleted
If the sprint is empty, it can be deleted directly with a simple confirmation.
11. Filtering
Work by User Summary
The "Work by User (in sprints)" section displays a row of chips showing workload distribution across your team:
What it shows - Total story points assigned to each team member
Scope - Aggregates points from all active and future sprints (excludes backlog)
Hover - Shows issue count and total points (e.g., "12 issues, 45 pts")
Click - Filters the view to show only that user's issues
This gives you a quick overview of how work is distributed across the team without having to expand each sprint.
Global Filter by User
Use the Filter by dropdown in the header
Select a team member's name
Only issues assigned to that person are shown across all sprints
Point totals are recalculated for the filtered view
Per-Sprint User Filtering
Filter issues within individual sprints by clicking on user chips:
Click a user chip - Filter that sprint to show only that user's issues
Multi-select - Click additional users to show multiple users' issues
Visual indication - Selected users are highlighted in blue
Filter status - Shows "Showing X of Y issues" when filter is active
Clear filters - Click the "Clear filters" button to remove all user filters
Tip
Per-sprint filtering is independent for each sprint. You can filter Sprint 1 to show Alice's issues while Sprint 2 shows Bob's issues.
User Capacity Mode
When in Per User capacity mode, the user chips serve dual purposes:
Single-click - Toggle filter for that user
Double-click - Edit the user's capacity limit
Quick Filter from Header Chips
Click on any name in the "Work by User" summary
The view filters to that user globally
Click again to clear the filter
Clearing Filters
Global filter - Select "All Users" from the dropdown, or click the X button
Per-sprint filter - Click "Clear filters" button in the sprint, or click each selected user again
12. Velocity Tracking
Track team velocity across completed sprints to improve capacity planning and forecasting.
Understanding the Velocity Panel
The Velocity Panel appears in the sprint view header and provides insights into your team's delivery capacity:
Expected Velocity - Predicted points for the current sprint based on historical performance
Trend Indicator - Arrow showing if velocity is improving (↑), declining (↓), or stable
Click to expand - View detailed statistics and sprint history
Velocity Statistics
When expanded, the panel shows four key metrics:
Metric
Description
Avg Velocity
Average points completed per sprint
Pts/Week
Average points completed per week (normalized for sprint length)
Efficiency
Percentage of planned capacity actually completed
Completion
Average completion rate across sprints
Team vs Per-User View
The velocity panel has two tabs:
Team Tab
Shows sprint history with:
Sprint name and dates
Sprint length (in weeks)
Capacity and completed points
Points per week (normalized)
Efficiency percentage
Best sprint marked with ★
Lowest velocity sprint marked with ▼
By User Tab
Shows individual team member performance:
User name - Team member
Sprints - Number of sprints participated in
Avg Planned - Average points assigned per sprint
Avg Completed - Average points completed per sprint
Efficiency - Individual completion rate (green if ≥90%, red if <70%)