Remove resolution from Jira issues that aren't actually resolved
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Jira Issues in your environment have been marked as resolved, but the issues themselves are not completed, and shouldn't have any resolution set.
You're looking to remove the resolution from the issues without touching other issue data.
If you need to set a resolution (instead of removing it), please refer to Configure resolutions in a Jira workflow.
Fix issues with incorrect Resolutions
Clear Resolution and Preserve Current Issue Status:
- Locate your Workflow:
> Issues > Workflows - Select Edit under Actions for your workflow
- You may want to create a Copy to preserve the original Workflow
- Create New Transitions that loop back into the same Status
- For example, from Open to Open
- On this New Transition:
- Select Add Post Function > Update Issue Field
- Select Resolution for the Field and NONE as the Field Value
- Publish Changes or Assign this workflow to your Project
Once created, you can use the Bulk Edit tool to perform this transition on all affected issues.
Clear Resolution By Re-Opening an Issue:
- Locate your Workflow: > Issues > Workflows
- Select Edit under Actions for your workflow
- Select your Re-Open transition, and select Post Functions
- Select Add Post Function > Update Issue Field
- Select Resolution for Issue Field and NONE as the Field Value
Unwanted resolutions are caused by Resolution field marked as required
The Resolution field has a Default value. When your field contexts mark the Resolution field as required, the field will be automatically filled with this value.
When the Resolution field is filled by any value at all, your issues will be marked as resolved. This is the reason why we recommend against any sort of "Unresolved" resolution as well.
- If the Resolution is set when an Issue is Created or Edited, check the Screen being used and ensure that the Resolution Field is not present
- If the Resolution Field is on a screen used for anything other than a "Resolve Issue" transition, the Resolution will be set to the Default Value
- If the Resolution is set during a Transition in the Workflow (for example: Open > In Progress), check that Transition for a POST Function that Sets the Resolution