Resolution field doesn't want to be "unresolved" during creation of an issue


I don't know how we mess the system but since 2 days each time we are creating a ticket/issue, the system refusing it and add to the screen the field "resolution" to force us to define a resolution status.

We don't want to "resolve" the issue at the creation.

This happens for all our projects whatever workflow/screen.

How to go back to the standard setup?


5 answers

1 accepted

0 votes
Accepted answer

The resolution field is not technically mandatory, but it does not have an "empty" value to select, so it always gets set if it is placed on a create or edit screen.

You must not put the resolution field on any create or edit field - only view or transitions into "end" type status.


If I understand it correctly, I would say that the field resolution is on the create screen.
Remove it from the create screen and it should be fine.

Thanks @Marcel Plomp.

No the field is not in the screen. But when I try to submit the issue to create it, it appears to request this field to be filled.

The only option for the field Resolution is that it can be hidden. So maybe it is on the screen, but as a result of the settings, you will not see it.

The field is always mandatory. This cannot be changed as such an option is not available for the JIRA admins.


>The field is always mandatory

I'm afraid that is incorrect.  The resolution field is NOT mandatory in JIRA terms.  It is optional.  It must be optional, because the users need to leave it empty until such a time as an issue is resolved.  The definition of a mandatory field is "it must have data in it".

So, the field is optional

If you put it on a screen that allows updating an issue though, then your users will fill it in because it always has a default setting, and no option to let them leave it blank.  Which is why you never put it on the create or edit screens, only transition screens to "end" status.

Your right. It is not mandatory.....but when it is on a screen you always have to select an option (or accept the default). So users experience this as a mandatory field as you can not leave it blank.

So you could say that is mandatory but not in the absolute sense of JIRA.

Hi All,

I have admin rights and I am trying to configure fields in order to make resolution optional, in field configuration page/ Resolution, there is no optional or required tab to be clicked, do you have any idea how can I make resolution optional?


As described earlier, you can not do it.

You need to remove it from create and edit screens.

Hi everyone,

One of my colleagues added the field "resolution" to most of our projects... So thanks for your help, it helped us to point the human issue.


Not quite.

They added "resolution" to some of your Screens.  The field exists on all your issues (and hence projects) automatically.  It's always there.

0 votes
Joseph Pitt Community Champion Jun 28, 2017

As Nic said, ANY time the field is presented on an edit screen it must be populated. It should ONLY be put on the transition screen used to set it. It will automatically appear in the issue details so there is no need to put it on any other screen than the transition ones. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,160 views 5 10
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you