Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to reset resolution in dropdown list to "Please select..."

Igor Koposov July 6, 2018

Hi!

 

On the last step ("Done") in our workflow everyone must choose correct resolution (we use Resolve screen) but there is current resolution (like - "QC passed") on the top of the list and sometimes people automatically leaves current resolution but really they must choose something like "Cancelled".

Is there a way to reset the list to prevent a human factor? "Please select..." must be on the top of the list.

 

Thanks!

2 answers

1 vote
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 6, 2018

You can't do this.  Resolution always has a default value and is always set when it is placed on a screen that allows edits of fields.

0 votes
Manon Soubies-Camy
Community Champion
July 6, 2018

Hello Igor,

I guess "QC passed" is the default value - you need to clear it:

  1. Go to the admin menu > Resolutions : https://yoursitename.atlassian.net/secure/admin/ViewResolutions.jspa
  2. Click on "Clear defaults"

clear.png

Hope this helps!

- Manon

Igor Koposov July 6, 2018

Nope...

Sorry, it didn't help :(

Manon Soubies-Camy
Community Champion
July 6, 2018

That's weird because I've tried it on my Cloud instance before, and I do have "Please select..." when I clear defaults!

- Manon

Igor Koposov July 6, 2018

I've cleared defaults and got the same resolution on the top of the listjira_resolution.png

Manon Soubies-Camy
Community Champion
July 6, 2018

I do trust you when you say it doesn't work :) but on my Jira Cloud, when I clear default, I always have "Please select..." (even if I've already set a resolution on another issue, it doesn't memorize it and stays on "Please select...").

@Nic Brough -Adaptavist- seems pretty sure about it, so I don't know if it's worth opening a ticket to Atlassian support? I don't get why it would work on my end and not on yours :/ and can't find anything about it in the documentation.

Suggest an answer

Log in or Sign up to answer