Scheduling
Part of Agile project software
Checking how a tool handles unfinished sprint work
At sprint end, unfinished work needs a decision: return it to the backlog, carry it into a future sprint or split it when a genuinely completed part can stand on …
Use one partly finished item, one untouched item and one parent with an unfinished sub-task as test cases. Note each item’s status and sprint, then check where unfinished work goes and what the tool records after the sprint ends. Don’t mark unfinished work Done just to close the sprint.
In Jira, this completion procedure applies to company-managed spaces. To check the space type, select More actions (•••) beside the space name in the header or sidebar; the space details appear at the bottom of the menu. Closing a sprint requires Jira Administrator access or the Manage Sprints permission.
From the space sidebar, open Active sprints and select the sprint from the drop-down if needed. With multiple active sprints, the Complete Sprint button appears only after you select one. Select Complete Sprint to begin closing it.
Check sub-tasks before closing: Jira requires all sub-tasks to be marked Done. Jira counts an item as complete only when it is in the board’s last column; items in other columns are incomplete. A parent item not marked Done moves to a future sprint or the Backlog when the sprint is completed.
For the test, leave the partly finished and untouched items outside the last column. In the completion dialog, choose Backlog, Any future sprint or New sprint; the last option creates a sprint and moves the items into it. If the sprint is shared across boards, only incomplete items from the board closing it move to the future or new sprint; incomplete items from other boards go to the Backlog.
Open the board’s Reports menu, select Sprint Report and choose the completed sprint. Check Issues Not Completed for unfinished items. The report reflects board column settings and issue history: changing a status mapping can change whether an item appears completed, and an item moved to another sprint can appear in a later sprint’s burndown with 0 Story points.
Jira does not mark work items with the date the sprint was closed. To find when a sprint ended, view the sprint for a work item. If you split a partly completed story because a completed part can stand alone, check each resulting item’s status and sprint assignment separately.
In Azure Boards, review the sprint backlog or sprint taskboard. Incomplete work should not remain assigned to a sprint whose end date is in the past, and Azure Boards does not automatically move incomplete items or reset Remaining Work to zero. Reassign unfinished items manually; for items not started, the guidance gives the product backlog or next sprint as destinations.
After reassigning Azure Boards work, check its sprint assignment and Remaining Work. Only completed work counts toward velocity, so unfinished work does not count in that sprint’s velocity.
How Jira and Azure Boards Handle Unfinished Sprint Work
- ToolJira (company-managed)
- Unfinished items after sprint endMoved to Backlog, future sprint, or new sprint (if selected); parent item not marked Done moves to Backlog or future sprint
- Sub-task completion requirementAll sub-tasks must be marked Done before sprint can close
- Automatic reassignmentNo – requires manual action to reassign or move items
- Velocity contributionOnly completed work counts; unfinished items do not count toward velocity
- Sprint end date trackingNot recorded on work items; view sprint details to find end date
- ToolAzure Boards
- Unfinished items after sprint endRemain assigned to past sprint unless manually reassigned; no automatic movement
- Automatic Remaining Work resetNo – Remaining Work is not reset to zero automatically
- Recommended destination for incomplete itemsProduct backlog or next sprint (manual reassignment required)
- Velocity contributionOnly completed work counts; unfinished items do not contribute to velocity
- Sprint end date trackingNot recorded on work items; use sprint details to determine end date
Steps to Close a Sprint in Jira (Company-Managed Space)
- Verify space typeSelect More actions (•••) beside the space name; check if it’s company-managed
- Access Active sprintsFrom the sidebar, open Active sprints and select the target sprint from the drop-down
- Check sub-tasksEnsure all sub-tasks are marked Done; incomplete sub-tasks prevent sprint closure
- Complete the sprintSelect Complete Sprint; confirm the dialog appears
- Choose destination for unfinished itemsIn the completion dialog, select Backlog, Any future sprint, or New sprint (creates a new sprint)
- Review sprint reportGo to Reports > Sprint Report > select completed sprint; check Issues Not Completed
Pre-Closure Checklist for Sprint Work in Jira and Azure Boards
- Verify all sub-tasks are complete (Jira only)Required before closing sprint in Jira
- Confirm items are not stuck in last columnPartly finished items should not be in the last column; they are considered incomplete
- Reassign unfinished items manuallyBoth tools require manual reassignment; no automatic movement to backlog or future sprint
- Reset Remaining Work (Azure Boards)Manually set Remaining Work to zero for items not started
- Check sprint assignment post-reassignmentEnsure unfinished items are correctly moved to backlog or next sprint
- Do not mark incomplete work as DoneAvoid falsifying completion to close the sprint
Key Metrics for Sprint Completion in Jira and Azure Boards
- Items counted in velocity
- Only those fully completed and in the final board column
- Unfinished items not counted
- Do not contribute to velocity in either tool
- Sprint end date visibility
- Not stored on individual work items; check sprint details
- Automatic movement of items
- None – both tools require manual intervention
