Manage the full sprint lifecycle for a Jira scrum board using jirac.
Steps:
- Check that
jiracis available by runningjirac --version. If missing, tell the user to install it (cargo install jira-commands). - Identify the operation:
- List:
jirac issue sprints -p <PROJECT> - Create:
jirac issue sprint-create -p <PROJECT> --name '<NAME>' [--board-id <ID>] [--goal '<TEXT>'] [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD] - Start:
jirac issue sprint-start <SPRINT_ID> - Complete:
jirac issue sprint-complete <SPRINT_ID> - Update:
jirac issue sprint-update <SPRINT_ID> [--name '<NAME>'] [--goal '<TEXT>'] [--start-date YYYY-MM-DD] [--end-date YYYY-MM-DD] - Delete:
jirac issue sprint-delete <SPRINT_ID>(destructive — confirm intent) - Run
jirac issue sprints -p <PROJECT>first when the user does not give a sprint ID — the list shows IDs and current state (future / active / closed). - Confirm intent before
sprint-start,sprint-complete, andsprint-delete— these change visible board state for the whole team.
Notes:
- A board can only have one active sprint at a time.
sprint-startwill fail if another sprint is already active. sprint-completecloses the sprint; any unfinished issues should be moved to a future sprint before completing.sprint-deletepermanently removes a sprint and detaches its issues from the sprint field — irreversible.- For a snapshot of work in a sprint (without changing state), use
jirac issue sprint-summary -p <PROJECT> --sprint '<NAME>'instead.
Examples:
- "list sprints in PROJ" →
jirac issue sprints -p PROJ - "create Sprint 25 in PROJ" →
jirac issue sprint-create -p PROJ --name 'Sprint 25' --goal 'Ship auth v2' - "start sprint 42" →
jirac issue sprint-start 42 - "complete the current sprint in PROJ" → list sprints to find the active ID, then
jirac issue sprint-complete <ID> - "rename sprint 42 to 'Sprint 25 (extended)'" →
jirac issue sprint-update 42 --name 'Sprint 25 (extended)' - "delete sprint 99" →
jirac issue sprint-delete 99(after confirming)