Forums

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

Required fields

Jeffrey Wood February 8, 2023

The resolution field isn't required but when I add it to the fields for a ticket submission, it says it required.

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.
February 8, 2023

Technically, the resolution field is not "required" like the other fields can be flagged in Jira's field configuration schemes.

It just works a bit differently to other select lists.  

Most of Jira considers resolution to be the "definition of done".  If it is empty, the issue needs attention.  If it has any value (including "unresolved" when inexperienced admins add that to the list), then the issue is resolved.

Jira Software is a little different - it looks to the last column of a board to be the "definition of done for the team using the board".

But you'll notice that, unlike all the other select lists in Jira, resolution does not have a "none" option.  You cannot blank it out, if it's editable, you have to set it.

If you put a resolution on a create/edit/transition screen, then your users will resolve the issue because they cannot leave it blank.

You should never put it on a create or edit screen, and you should never make it mandatory in the field configuration.  It should only be used in transition screens that are used to "close" issues.

1 vote
Mikael Sandberg
Community Champion
February 8, 2023

This is expected behavior, any time you add the Resolution field to a screen it will automatically be required. 

The Resolution field is an important feature in Jira. It specifies the reason an issue is closed and removes the need of having multiple statuses with the purpose of stating why the issue is closed, thus capturing important data for your team while reducing the time you have to manage your workflow.

Jira considers that the lifecycle of an issue has come to an end when the Resolution field has a value, and many native features in Jira depends on the Resolution field.

Jeffrey Wood February 8, 2023

Thanks for the feedback.  The issue is when the resolution field is filled in when the ticket is created, it puts a closure date as well.  This makes it difficult to track issues based on closure date.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events