Boards & Sprints¶
Manage Scrum and Kanban boards, sprints, and backlogs.
Boards¶
List Boards¶
Options:
| Flag | Description |
|---|---|
--project | Filter by project key |
--type | Filter by type: scrum, kanban |
--name | Filter by name pattern |
--limit | Maximum results |
Examples¶
# All boards for a project
atlcli jira board list --project PROJ
# Only Scrum boards
atlcli jira board list --type scrum
# Search by name
atlcli jira board list --name "Team"
Get Board¶
Output:
Board: Team Scrum Board
ID: 123
Type: scrum
Project: PROJ (Project Name)
Filter: 10001
Columns:
- To Do
- In Progress
- Done
Board Issues¶
Get all issues on a board:
Options:
| Flag | Description |
|---|---|
--id | Board ID (required) |
--status | Filter by status |
--limit | Maximum results |
Backlog¶
View the backlog for a board:
Options:
| Flag | Description |
|---|---|
--id | Board ID (required) |
--limit | Maximum results |
Sprints¶
List Sprints¶
Options:
| Flag | Description |
|---|---|
--board | Board ID (required) |
--state | Filter: active, future, closed |
--limit | Maximum results |
Examples¶
# Active sprints only
atlcli jira sprint list --board 123 --state active
# Future (planned) sprints
atlcli jira sprint list --board 123 --state future
Get Sprint¶
Output:
Sprint: Sprint 14
ID: 456
State: active
Board: 123 (Team Scrum Board)
Start: 2025-01-06
End: 2025-01-17
Goal: Complete API refactoring
Issues: 24 (18 done, 4 in progress, 2 to do)
Points: 21 committed, 16 completed
Create Sprint¶
Options:
| Flag | Description |
|---|---|
--board | Board ID (required) |
--name | Sprint name (required) |
--start | Start date (YYYY-MM-DD) |
--end | End date (YYYY-MM-DD) |
--goal | Sprint goal |
Examples¶
# Create with dates
atlcli jira sprint create --board 123 --name "Sprint 15" \
--start "2025-01-20" --end "2025-02-03"
# Create with goal
atlcli jira sprint create --board 123 --name "Sprint 15" \
--goal "Complete user authentication feature"
Update Sprint¶
atlcli jira sprint update --id 456 --name "Sprint 14 - Extended"
atlcli jira sprint update --id 456 --goal "Updated goal"
atlcli jira sprint update --id 456 --end "2025-01-20"
Start Sprint¶
Start a planned sprint:
Complete Sprint¶
Complete an active sprint:
Options:
| Flag | Description |
|---|---|
--id | Sprint ID (required) |
--move-to | Sprint ID for incomplete issues |
# Move incomplete issues to next sprint
atlcli jira sprint complete --id 456 --move-to 457
# Move to backlog (default behavior)
atlcli jira sprint complete --id 456
Add Issues to Sprint¶
Remove Issues from Sprint¶
Move issues back to backlog:
Sprint Report¶
Get comprehensive sprint metrics:
Options:
| Flag | Description |
|---|---|
--id | Sprint ID (required) |
--format | Output: table, json, markdown |
Output:
Sprint 14 Report
================
Duration: Jan 6 - Jan 17, 2025 (10 days)
Status: Active
SUMMARY
-------
Total Issues: 24
Completed: 18 (75%)
In Progress: 4 (17%)
Not Started: 2 (8%)
STORY POINTS
------------
Committed: 21
Completed: 16
Remaining: 5
SCOPE CHANGES
-------------
Added: 3 issues
Removed: 1 issue
TOP CONTRIBUTORS
----------------
Alice: 8 issues completed
Bob: 6 issues completed
Carol: 4 issues completed
Export Sprint Report¶
# Markdown for documentation
atlcli jira sprint report --id 456 --format markdown > sprint-report.md
# JSON for automation
atlcli jira sprint report --id 456 --json
Ranking¶
Rank Issues¶
Change issue order in backlog or sprint:
# Move before another issue
atlcli jira rank PROJ-1 --before PROJ-2
# Move after another issue
atlcli jira rank PROJ-1 --after PROJ-3
JSON Output¶
All commands support --json:
{
"schemaVersion": "1",
"sprints": [
{
"id": 456,
"name": "Sprint 14",
"state": "active",
"startDate": "2025-01-06",
"endDate": "2025-01-17",
"goal": "Complete API refactoring",
"boardId": 123
}
]
}
Best Practices¶
- Plan sprints in advance - Create future sprints so issues can be assigned
- Set sprint goals - Clear goals improve focus
- Use sprint reports - Review metrics to improve velocity
- Move incomplete work - Use
--move-towhen completing sprints