jira.field.resolution.include still shows unwanted resolutions

[Caleb TeBokkel]

I've set up jira.field.resolution.include for a Transition Property on a specific workflow. I have set this property in different ways to try and get it to work.

I've tried limiting the field to a single value as shown in the screenshot. I've also tried using comma-delimited values like this:

10001,10003,10004,10005,10006,10007,10008,10009

Please help point out what I'm doing wrong. Thank you!

*Update - I've also tried the inverse, using jira.field.resolution.exclude with the same result.

[Trudy Claspill · Accepted solution]

Hello @Caleb TeBokkel 

Try using jira.field.resolution.exclude to exclude the Resolutions that you don't want to appear in the list.

[Caleb TeBokkel]

I've tried that as well with the same result. Sorry I should have included that in the original post.

[Trudy Claspill]

The property is applied to a Transition. That means it will affect the values only during that Transition. And it is intended to affect the values that show in the Transition Screen.

When you are viewing the issue and pull-down the Resolution field as you have, that will not be affected by setting the property in a Transition in the workflow because in this case you are not executing any transition.

On a side note, I see that one of the values you have is "Unresolved". Note that an issue is considered "resolved" by Jira logic if the Resolution field contains any value regardless of what the value is. Even if the value says "Unresolved" Jira logic will consider that issue "resolved" for purposes of things like the "Created vs. Resolved" report.

To note that an issue is "unresolved" the Resolution field must be cleared (have no value at all). You can clear the Resolution field by adding a Post Function in your workflow Transitions when the issue is transitioning to a "not done" status.

[Caleb TeBokkel]

So there is no way to limit the resolutions available when editing an issue? I tried to associate specific resolutions to specific statuses and that did not work as intended either.

Unresolved isn't a resolution, it's the default hard-coded value. It just shows on the button because it is the default. 

[Trudy Claspill]

Have you added the Resolution field to the Screens (in the Screen Scheme(s) in the Issue Type Screen Schemes) used by this project? The field should not be editable at all in the Issue View unless you added the Resolution field to the Screens.

I am curious as to why you added the Resolution field to the screen.

With some experimentation I discovered that if you have added the Resolution field to your Edit Screen, and if the Resolution field has no value, then it does indeed show "Unresolved" there. So I learned something new!

There is no native method that I'm aware of to limit the Resolution values that are available from the View/Edit Issue screen when you include the Resolution field on that screen.

[Caleb TeBokkel]

Ahh, very nice. I didn't even realize I could remove Resolution from the screen entirely, I assumed it was a hardcoded Jira field. 

I have done that. Thanks for your help!

[Trudy Claspill]

You're welcome!

If my responses have helped you resolve your question, please consider clicking on the Accept Answer button. That will mark your post as Solved, which helps others searching for answers find the posts with validated responses.