Forums

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

The resolution field for Bugs and Stories is a required field but not set to be

Kirk Stevens June 7, 2018

When creating a bug and/or story or for any work item for that matter, we have to apply a resolution because it is deeming it to be a required field. When I have reviewed the Fields configuration for the project, it is not set to be a required field. 

Bug shot

Resolution Field in Bug.PNGResoltion in Fields Configuration.PNG

 

2 answers

1 vote
Thomas Schlegel
Community Champion
June 7, 2018

Hi @Kirk Stevens,

maybe you have set the resolution field on your create-screen. Even if you don't edit the field there, a default resolution will be set.

Have a look also at your workflow, escpecially the validators of your create-transition. Maybe there is a check for the resolution field.

Kirk Stevens June 7, 2018

Thanks guys, may seem basic but new to the product

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.
June 7, 2018

It's not technically mandatory, but it gets a value selected when placed on an edit screen.

What you need to do is remove the field from the "create" issue screen (and "edit" if you have it there)

The resolution should only ever be put on "transition" screens in transitions going from "open" type status to "closed" type ones.  That's the only place you want to set the resolution.

Kirk Stevens June 7, 2018

Thanks guys, may seem basic but new to the product

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.
June 7, 2018

It's also an exception to the way all the other fields behave, which adds more confusion!  Although it's a "basic" part of the way Jira works, I wouldn't say it's obvious or intuitive. 

I don't think I know of an admin who has got this first time they've run into it, we've all either had someone explain it to us, or worked it out ourselves by getting it wrong the first time we use it!

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events