nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Issues have a status of "CLOSED" but a resolution of "UNRESOLVED". Need to change "UNRESOLVED" to "FIXED"

Robert Quirion

We had implemented a workflow and in the process realized that we forgot to include the Resolve form before closing an issue. Now I am left with 93 Issues that I am unable to flip from 'UNRESOLVED to FIXED

I did a lot of research and I have been unsuccessful in finding a way to change it unless Altassian gets involved to help out.

I want them switched to FIXED so that they no longer show on my project dashboard as unresolved.

Thank you for your assistance.

Accepted answers

Teck-En

Most likely the closed transition do not have the resolution field in the screen. You might want to add another transition in closed step with resolved screen(it has resolution field) then use bulk transition to transit them and add the resolution to those issues.

All comments

Harry Chan5

Hi, you can do a search of all the oustanding issues you need and do a bulk edit of them (if resolution is edtable in edit screen) or you can create a temporary transition that changes the resolution and bulk transition them.

Teck-En

Norman Abramovitz

You need to modify your workflow to allow editing in closed state as noted in this article

https://confluence.atlassian.com/display/JIRA/Allow+editing+of+Closed+Issues

As noted above you need to make sure the screen used for closed includes the resolution field.

You should be able bulk edit in closed state.

David Skreiner2

This happens all the time unfortunately: Users aren't perfect, so they often forget to change "Unresolved" to the correct resolution when closing an issue.

So we'd really need to be able to tell JIRA to make the Resolution field Required, but only for the Resolve and/or Close transitions.

At last, after many years, Atlassian seems to have added this to the roadmap: https://jira.atlassian.com/browse/JRA-5783

Barney_ukqsny

I would really recommend the Adaptavist ScriptRunner plugin for this (and many other admin functions). Use the 'Bulk Fix Resolutions' built in script to sort this out with a single click. No need to fiddle around under the hood with workflows. See https://scriptrunner.adaptavist.com/latest/jira/builtin-scripts.html

Barbara Hamde

hi, how can I add the resolution field? I can't see that option while editing the workflow

Barney_ukqsny

See "Setting the resolution field" in https://confluence.atlassian.com/adminjiraserver/working-with-workflows-938847362.html#Workingwithworkflows-SettingtheResolutionfieldSettingtheresolutionfield

You either need to set it via a post function or get the user to set it via a transition screen.

A post function is useful if you always want the same value set for a given transition.
Using a screen is useful if you need the user to select a particular resolution.

https://confluence.atlassian.com/jirakb/jira-issues-need-a-resolution-826873869.html has a nice summary of this.

Godwin Omughelli

Another way of solving this is to create a new project board with a proper workflow and post function set. Ensure that the workflow has reopen issue as a status.

After moving, reopen the issue, then mark as done. I just did it.

Thanks

Beth Starr_ozjkiw

Simple fix... create a transition from the closed status to the closed status. If the issues should have all the same resolutions, then set it with a post function. Bulk edit and transition the issues using the newly created transition. Go back and remove the transition if no longer needed.

If the issues should have different resolutions, then on the newly created transition add the resolved screen. Bulk edit the issues and transition using the new transition and select the resolution. Remove the new transition if it is no longer needed.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

workflow

status

resolution