How to make the Resolution field mandatory in the Resolve issue screen

Kapil Podduturi October 14, 2021

Hello Community,

I need your help in resolving a situation I am in. 

Requirement: Make the resolution field mandatory when closing a Story.

Steps taken:

  • Edited the workflow. Added Resolve issue screen to the Closed Transition.

Edit workflow.png

  • Resolve issue screen has 'Resolution' field.

Resolve Issue screen.png

  • Tried by making the Resolution mandatory on the Closed transition by using validators.

Validator.png

All these are not making the Resolution field mandatory.

Also, cannot find how to make the field mandatory from the field configuration used by the project. Required - button is missing

Field Configuration.png

 

Resolve issue Screen when trying to close the Story.

Popup screen.png

3 answers

1 vote
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 15, 2021

Um, actually, you don't need to do any of this.

If you put the resolution field on a transition screen, it will be filled.  The person closing the issue cannot leave it blank.

Kapil Podduturi October 15, 2021

Hi, @Nic Brough -Adaptavist- I added the Resolve Issue screen as the transition screen and the Resolution field is part of it. I wanted to make it mandatory and hopefully make None as the default. Currently Done is the default value for the Resolution field. Screenshot is attached above in the question.

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 15, 2021

Ok, there's an important point here that I think I need to explain totally differently:

You say "I wanted to make it mandatory and hopefully make None as the default" 

Resolution does not have a "none" value.  You can't make it a default because "none" is not an option for it.

"None" is what Jira displays for most select lists when they have no data and you don't want to fill anything in.  Resolution is different - it can be empty, but "none-meaning-empty" is not offered to people, a value is selected in updates.

If the resolution is on a screen where it can be entered, then it will have the current value selected, or if it is empty, it will have the default selected.

Either way, the person updating the issue will set the resolution to something.

You do not need to make it mandatory, it will always be filled by the update.

Like Dennis Gerritse likes this
Kapil Podduturi October 15, 2021

Hi @Nic Brough -Adaptavist-, thanks for your reply. I agree with what you said and 100% agree.

Please see the attachment below (this is from the JIRA server). I wanted something like this and if it is possible to do on cloud version.

Use 'Please Select' as default and make the field mandatory - Asterisk in Red.

2021-10-16_12-54-18.png

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 15, 2021

I do not know how to explain this another way.

There is no option for "none", "please select" or any other phrase that means "resolution does not have a value".

You do not need one.  You do not need to make anything mandatory.  You do not need to do anything other than put the field on the transition screen (and never put it on a screen used for create or edit)

Kapil Podduturi October 15, 2021

ok, thanks @Nic Brough -Adaptavist- .

Jyothi Ravipati October 11, 2022

Hi Kapil,

Did you find any solution for it? As I was looking for the same.

 

Thanks in Advance

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 12, 2022

The "solution" is to use the field as intended, as described in my answers and comments.

Edward Vitalos January 3, 2023

This answer makes no sense. There are many cases where its helpful to provide additional details for a resolution so you can search by a resolution value. You can set other fields with a default value and make them require a change from the default value during a transition to Done Status. Why not this one? 

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 3, 2023

The answer explains how the resolution field works, I'm not sure what does not make sense to you.

Resolution works differently to other fields because it is intended for a different purpose than most - it tells Jira when an issue is resolved, with a brief generalised phrase about why.  The "can't leave it blank during an edit/create/transition" is deliberate - it makes it easier for a developer to resolve an issue when it needs to be resolved. 

If you want to provide additional details, fine, add another field and put a validator on it to make it mandatory during a "close" type transition.

I don't think the way resolution works is a good way to do open-and-closed in Jira, it does confuse a lot of new admins, but I do see that it gives us a lot of flexibility, and I'm not sure how I would redesign it.

David Guthrie
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 12, 2023

Here is my issue with how the Resolution field works. Since it is pre-filled and not madatory to change, when closing a Jira it easily gets mislabeled as say "Fixed" (default) when it should be "Can't Reproduce".

In human nature, if something is pre-filled and you are not required to take action on it, it is easily overlooked. That is why it would be better to have the Resolution field as suggested above with "Please select...". That way each time a Jira is closed, the user must take active action to choose the right resolution rather than Jira automatically selecting a default resolution that may not apply. This causes a ton of mis-categorized resolutions. 

 

Anyone have workarounds to this issue?

Like Laura Lasser likes this
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 13, 2023

There are no "workarounds", it's not considered to be an issue, because it is working as intended.

Edward Vitalos May 15, 2023

This work around worked for me.

  1. Remove the Resolution field from all views but the Closed screen.
  2. Remove the default value for the Resolution field.
  3. Set a Validator up so that the Resolution field must be changed when transitioning to Closed.

Now all techs need to select a Resolution from the Resolution drop down list to close the ticket.

Like Laura Lasser likes this
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 15, 2023

Again, you really do not need to do this.

The resolution field is always defaulted when on-screen, and you do not need a validator to enforce change.

Kolja Sulimma
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 13, 2023

I can't confirm this. 

When I open the resolve issue screen for an issue that has resolution set to "keine Lösung" (no resolution, but in German), the drop down list does not show that the current field value is "keine Lösung" and it also does not offer "keine Lösung" as a possible value for the field.

Instead it chose all other possible field values as options with a heading "bitte auswählen..." (please choose). 

This suggest that a choice between the shown options must be made. 
Maybe it is the intended behaviour to keep "keine Lösung" as the field value if no choice is made, but in this case the user interface design is broken: It suggest a choice must be made, it does not indicate the current value and it does not show what the result of your action will be.

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 16, 2024

You don't need to do any of that, please read the answer above.

0 votes
k-p May 10, 2023

in resolve issue screen i added a validator! but it doesnt worked in request portal when i am clicking on resolve this issue. so does workflow validator words on portals? if yes, then how?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events