nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Resolution Built-In Field is Always Required

Anthony Wu

The built-in resolution field is always required if you put it on any screen. Any reason why? We can't put it on the Edit Issue Screen because it is required, but then that limits you from being able to go back and modify the resolution if you messed up setting it in the transition screen.

Is there anyway to make this not required? Or at least be able to pick the Unresolved state. Because that would be ideal.

And I think people have mentioned before to put Unresolved as a state, but this presents confusion when searching for issues in the issue navigator since there will be two Unresolved states in the Resolutions select box. Plus, if you have a link to that ticket from somewhere else, it appears as crossed out. So that really isn't a good solution.

Thanks!

Accepted answers

JamieA

The resolution field is intrinsically related to your workflow, so it doesn't make any sense to put it on an edit screen. All of your states should either map to resolved (possibly a specific resolution) or to unresolved. If that's the case you should only put it on a transition, or unset it using a post-function, from closed -> open for instance.

The worst possible idea is to create a resolution called Unresolved. More info here which is still not out of date: http://blogs.onresolve.com/?p=84

All comments

NielsJ

Usually we have a transition named "Re-Set resolution" or so in the final state of our workflows. On the transition screen you can only modfy the resolution and add a comment. So you never get "trapped" ;-)

Another idea might be to add a Validator to your final workflow steps that define the resolution as a required field.

JamieA

The worst possible idea is to create a resolution called Unresolved. More info here which is still not out of date: http://blogs.onresolve.com/?p=84

Vishnukumar Vasudevan

Hi,

I think you need to look in to the 'Field Configurations' for this issue type. You might have set 'resolution' as required there.

So the fix is, make it 'Optional' there and use validators to have resolution mandatory in any transitions.

Thanks, Vishnu.

Reza Khosravi

Hi @Vishnu,

Resolution is a SYSTEM Field and it's always required, you cannot make it optional from Configuration scheme.
Based on what I find in atlassian, it's better to not have "Resolution" in edit screen and try to change it through the transitions.

Gurpreet_cqt1ju

@Vishnukumar Vasudevan he is talkign about resolution field bro. it is a built-in field and you CANNOT set it to optional. please read the question carefully before posting. thanks

Nic Brough -Adaptavist-

Nope. It's optional in the field config.

Have another read of the question - the first sentence is correct (still - you're posting on a 6 year old question!).

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

workflow

resolution