Split Unfinished Jira Sprint Issues
Split work only when you can define a coherent completed outcome and a separately actionable remainder. Use the backlog split controls rather than pretending an unfinished issue is complete for reporting.
Step-by-step guide
Check access and scope
Splitting applies to supported software backlog views, not every Jira space or board surface. Agree on acceptance criteria and estimate treatment with the team.
Inspect accepted behavior
Review the original acceptance criteria and evidence of completed behavior.
Define the remaining outcome
Identify a meaningful remaining outcome without rewriting history.
- Worked example: If invitation creation works but recovery does not, split only when creation is independently releasable under the agreed scope. Keep incomplete security checks attached to the work they actually constrain.
Open the backlog
Open the relevant Scrum or enabled Kanban backlog.
Split the work item
Use Split work item and choose an appropriate destination for the new work.
Reconcile both records
Reconcile criteria, estimates and links across both records.
Verify the result
Both records have clear nonoverlapping criteria and the remaining work has a real owner and destination.
Common mistakes
Check the handoff edge case
Copying all acceptance criteria to both records obscures the split. Make the completed and remaining outcomes nonoverlapping.
Sources and verification
Based on product documentation checked on 2026-10-24. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.