Trouble with jira.field.resolution.exclude and xxx.include

[Karin Stevenson]

Our system (Server 7.4.2) is used by a number of teams that added different resolutions which are completely meaningless and even detrimental to the workflow in our team. I've been trying to restrict the resolutions that show up with jira.field.resolution.include as well as jira.field.resolution.exclude.

In my workflow I have a step called "Completed" with "Allow all statuses to transition to this one" checked.

The "All" transition has the "Resolve Issue Screen" set and a property to exclude resolutions: jira.field.resolution.exclude 10200,10100

where the 10200 and 10100 and the id's I can see when I hover of the Edit link for these Resolutions. I tried

jira.field.resolution.exclude 10200,10100

jira.field.resolution.exclude=10200,10100

jira.field.resolution.exclude (10200,10100)

jira.field.resolution.exclude=(10200,10100)

None of them makes a difference. When I click on the Completed button for an issue the Resolve Issue Screen shows up but all resolutions show up, even the ones specifically excluded. 

The same happens when I try to do the jira.field.resolution.include with the values that I want to see. Of course,  I deleted the exclude property first. For some reason neither one seem to have any effect.

I also tried to set up a custom screen instead of using the standard Resolve Issue Screen. Same result--all resolutions in the system show up in the Resolve screen.

Could somebody please provide some guidance on what I might have wrong? This is a really big problem for us.

Thanks in advance for your help!

Karin

[Ignacio Pulgar · Accepted solution]

I've tried it like this and it works like a charm:

[Ignacio Pulgar]

May you ensure the property key doesn't have any leading or trailing whitespaces?

[Timothy Bassett]

I also can confirm that this attribute does not work

[Dan Knapton]

Also make sure there re no spaces between Property Values in the list.

10200,10100 should work if there is no space after the comma

[Ignacio Pulgar]

Indeed! As Dan Knapton mentioned, it is key to ensure there were no spaces at all, not even after each comma!

[Joe Pitt]

first, I suggest you use the include. When you add new resolutions down the line you won't need to update the list.

Second, try re-indexing. 

[Karin Stevenson]

Thank you, Joe. That's what I did. That way I'm not subject to changes other people make in the system.

I also reindexed the project and the system, just for good measure.

Thanks again!

[Timothy Bassett]

The include attribute does not exist - https://jira.atlassian.com/browse/JRACLOUD-16443

[Brent Nye]

include apparently does exist in Data Center. Worked for me in 8.20.1.

[Karin Stevenson]

First: Thank you all for the super quick responses and help, Gentlemen!

And I'm blushing to admit that I did have a trailing space. I thought I had checked this but with all the back and forth it must have crept back in.

It's working great now! 

Thanks again and Happy Holidays to you all.

Karin

[Alexey Matveev]

Hello,

Do you publish your workflow after changes?

[Karin Stevenson]

Hi Alexey,

Yes, workflow is published after changes and project reindexed.