Sprints
A Sprint is a time-boxed period during which the team commits to completing a set of issues. Axoria uses sprints to organize iterative work and measure progress over time.
Lifecycle
FUTURE → ACTIVE → COMPLETED
| Status | Description |
|---|---|
| FUTURE | Sprint created but not yet started |
| ACTIVE | Sprint in progress (only one active sprint per project) |
| COMPLETED | Sprint finished with metrics available in reports |
Only one sprint can be ACTIVE at a time per project.
Creating a Sprint
- In the project sidebar, go to Sprints.
- Click + New Sprint.
- Fill in:
- Name (required - e.g., "Sprint 3 - Reports Module")
- Goal (optional - the sprint's objective in one sentence)
- Start date and End date
- Click Create Sprint.
Adding Issues to a Sprint
From the issue panel
- Open the issue.
- In the Sprint field, select the desired sprint.
From the backlog or list view
- Select one or more issues.
- Use Move to Sprint from the context menu.
Issues can be moved between sprints at any time before the sprint is completed.
Starting a Sprint
- Find the sprint with status FUTURE in the sprint list.
- Click Start Sprint.
- Confirm the start details.
The sprint transitions to ACTIVE and the board automatically shows its issues.
To start a new sprint, the currently ACTIVE sprint must be completed first.
Completing a Sprint
- Find the ACTIVE sprint.
- Click Complete Sprint.
- Choose what to do with incomplete issues:
- Move to another future sprint
- Move to the backlog (no sprint)
The sprint transitions to COMPLETED and its metrics become available in Reports and the Timeline.
Sprint Goal
The goal is a short phrase describing the purpose of the sprint. It is displayed at the top of the board during the active sprint to keep the team focused.
Example: "Deliver the complete authentication flow and basic project setup."
Sprint Metrics
When viewing a sprint in the Timeline, you can see:
- Total issues / completed / in progress
- Story Points - total and completed
- Progress percentage (completed issues ÷ total × 100)
- Status distribution - issue counts per board column
Sprints and the Board
The Kanban board can be filtered by sprint to show only the issues assigned to that sprint. This keeps the view focused on the current iteration's scope.
Issues without an assigned sprint go to the backlog and are hidden from the board when a sprint filter is active.