Sprint Transition

When completing a sprint, unfinished issues need to be moved to another sprint or back to the backlog. Axoria automatically records this movement to ensure full traceability of work over time.

What Is Tracked

When a sprint is completed and issues are moved, the system automatically records the origin sprint for each migrated issue. This data is persisted on the issue and retained through future migrations.

"Moved" Badge

Issues that migrated from a previous sprint display a "Moved" badge on the board card:

• Orange/amber color to stand out visually
• Tooltip on hover shows: "Moved from sprint [original sprint name]"

The badge is displayed as long as the issue remains unfinished in the current sprint.

Sprint Completion Flow

1. Go to Sprints in the project sidebar.

2. Find the ACTIVE sprint and click Complete Sprint.

3. The system classifies issues:

   • Completed (DONE status): remain associated with the closed sprint in reports
   • Unfinished: you choose the destination

4. For each unfinished issue, select:

   • Move to another sprint (future) - the issue’s origin sprint is recorded
   • Move to backlog - issue has no sprint; origin sprint is still recorded

5. Confirm.

Traceability in Reports

In the Timeline, when selecting the completed sprint, you can see:

• How many issues were completed within the sprint itself
• How many were moved to the next sprint (with "Moved" badge)
• The full migration history of each issue individually

This helps identify sprint overload patterns and improve estimates over time.

Notes

• The origin sprint always points to the immediately previous sprint. If the issue is moved again, the field is updated to the sprint being completed.
• Issues in the backlog (no sprint) do not have an origin sprint recorded.
• This feature is automatic - no additional configuration is required.