Get rid of "Unresolved" resolution

[Satchidanand_CS_ext]

For some reason there exists "Unresolved" resolution in DNA's Jira along with the default Unresolved resolution. when we check to clear that resolution there are 4808 issues associated to it and not sure which is default and which is the created 'unresolved' one. Any ideas how to resolve this.

[John Funk]

Hi @Satchidanand_CS_ext 

Check the Resolution field. If the field is empty, that's the system labeling it Unresolved. 

I would think you would want to change your wording for yours from Unresolved to Won't Fix, Won't Do, We don't know what the crap is going on with this, etc. 

[Marc - Devoteam]

Hi @Satchidanand_CS_ext 

I made a custom resolution called Unresolved, to replicate your issue

What I see is the I can JQL on both.

resolution = Unresolved or resolution = "\"Unresolved\""

This is default in the system and not to use as a resolution when resolving an issue resolution = Unresolved

The resolution = "\"Unresolved\"" is able to be used on as a resolution.

Also via the API you can see, that the default resolution is not findable, but the custom one is

use the following API call: rest/api/2/resolution

I hope this answer will help you out

[Marco Brundel]

Hi @Satchidanand_CS_ext & @Marc - Devoteam ,

Making a custom resolution called Unresolved is in my opinion definitely not a good idea/advice.

As @John Funk mentioned,check the Resolution field. If the field is empty, that's the system labeling it Unresolved. 

And I like to refer to Nic Brough's response in this question.

Regards, Marco

[Marc - Devoteam]

Hi @Marco Brundel 

I just made to compare what @Satchidanand_CS_ext sees at the moment and how to resolve the current issue.

I'm fully with you that creating a resolution like resolved is a bad idea/advice

[Nic Brough -Adaptavist-]

Argh - no, never add "unresolved", or any other resolution that has a name that suggests it.

I've been yelling that for almost 20 years now!

• The resolution is a simple field.
• When the field in the database has <null>, the issue is unresolved. 
• When the field in the database has any other value, the issue is resolved.

If an inexperienced admin has added "unresolved" as a resolution option, then the best thing you can do is

• Work your way through all of your screens - make sure resolution is only on screens used for resolving/closing issues (or issue view - view is not a problem)
• Change the name of "unresolved" to "don't use this" or anything else that makes it clear it is the wrong thing to do
• Go through all your issues where they are (now) set to "don't use this" and clear the resolution for the ones that are still open (there's a pile of stuff you may have to do here, not worth the essay until you've found them all), and change the ones that are truly closed to a better resolution.
• Delete the "don't use this" resolution so people can't misuse it again.

[Satchidanand_CS_ext]

Thanks All for your Valuable responses, Ill take thinks in to consideration and work things out.