Fix Jira Resolution and Status Errors
Keep status and resolution consistent: active work should have an empty Resolution, while completed outcomes should receive an appropriate resolution through the workflow.
Step-by-step guide
Check access and scope
Workflow changes need authorized administration and representative testing. Diagnose the current issue set before repairing existing records.
Find inconsistent issues
Find done issues with empty resolution and active issues with a value.
Inspect completion transitions
Inspect transitions that enter and leave completed states.
- Worked example: An invite bug moved back to In progress must not retain Done as its resolution. Otherwise filters using resolution can treat unfinished work as already completed.
Set resolution behavior
Configure the correct resolution behavior in those transitions.
Test completion and reopening
Test completion and reopening on sample issues.
Repair historical exceptions
Repair historical exceptions with an approved procedure and check reports.
Verify the result
Completing sets the intended value and reopening clears it, with sample filters reflecting actual active work.
Common mistakes
Avoid the main failure mode
Do not create a resolution option literally named Unresolved. Jira treats an empty value as unresolved; a named value is still a resolution.
Check the handoff edge case
Repairing existing issues without fixing transitions lets the mismatch recur. Correct the workflow and then address historical records.
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.