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; } } }

jira.field.resolution.exclude doesn`t work

super cometa

I tried this short script to remove some resolutions but no one was removed.

I inserted this in Property Key of the workflow step. I doubled checked the resolution ID to make sure to use a proper value. Everything seems to be set as it needs.

I tried jira.issue.editable with false value and it worked.

I`m getting so frustraded.

Does anyone knows how to handle this issue ?

Accepted answers

RambanamP

Leading or trailing white spaces need to be trimmed in workflow transition properties entry boxes.

for examle

"jira.field.resolution.exclude " <strong>does not equal</strong> "jira.field.resolution.exclude"

All comments

Christian Czaia [Decadis AG]

you have to use the property on let's say the resolve "transition" where the field is present on the screen and it should work.

Cheers Christian

RambanamP

Leading or trailing white spaces need to be trimmed in workflow transition properties entry boxes.

for examle

"jira.field.resolution.exclude " <strong>does not equal</strong> "jira.field.resolution.exclude"

super cometa

Thanks a lot. I tested and it worked very well on a transition property.

My point is to remove the transition from the litte list that is shown up in edit window of the issue.

Bellow is the list that i mean.

https://confluence.atlassian.com/download/attachments/313467778/Resolution.png?version=1&modificationDate=1354859273339&api=v2&effects=border-simple,shadow-kn

super cometa

I took care of that. Thank you

Andy Jones_qty270

In case this helps anyone else who is struggling to work this out.

The property "jira.field.resolution.exclude" ONLY applies to Transitions in a Workflow.

You can set this property on a Status node, but it will have no effect. Further, Jira will not warn you that the property is not applicable. It just ignores it.

Background: Every Jira Issue has a current State. A Workflow is a directed graph, which shows the valid issue States (nodes), and the Transitions (edges) which link them. Transitions specify which States can move to which other States.

In the usual Issue view, the Transitions which are valid for the current State appear in the form of buttons, below the Summary line and above the Details section. If there are more than 3 outgoing transitions, then the third/last button will be named "Workflow" (instead of the name of a transition). This "Workflow" button will have a drop down select list containing the third, fourth etc transitions.

When a user views an issue, and clicks a transition button which leads to a State which is in the Done (green) category, then if there is Screen defined for this, this Screen will have a"Resolution" field. This is a mandatory field, and the values in the drop down list will normally be every Resolution within Jira (since they are global). However the Resolutions which show up are affected by the 'exclude' property.

Note that you have to use IDs, which you can see if you go to edit a Resolution - the ID is in the CGI parameters. This trick works for other attributes too.

Since this property applies to Transitions, and not to the source or destination States, then you have to edit EVERY transition which leads to ANY Done (green) state, and add the property to exclude Resolutions from the resulting screen(s).

Looking at this from a glass-partially-full perspective, I guess it means you have the granularity to explictly make different resolutions available, depending upon the current state and the destination state.

But in Jira, Resolutions are global, and this property is the only way to sort of make them per-project. If you just want to exclude a number of Resolutions which are inappropriate for a project, then editing every terminal Transition can be a lot of work, especially if you have multiple workflows, with multiple Done states, and lots of transitions which lead to them...

Joe Pitt

I suggest using the 'include' property instead for a couple reasons; 1. I've found there is usually a fewer number of resolutions I want to include than exclude, and 2. If I add a new resolution I only have to update the workflow where it is needed.

Joe Harmon_y3pgen

How do you do multiple? It works for one ID but not for multiple ID. I have tried comma delimited with and without a space between the IDs.

Peter Kerrigan

Hi @Joe Harmon, As this was from over a year ago perhaps you have figured this out. I was having the same issue but after some trialing of different methods I found one that works. The list of IDs that you want to include or exclude (depending on property) needs to be in a comma separated list with no spaces. For example, resolution IDs listed need to look like this: 10100,10200,10300.
As you can see, no spaces between the resolution IDs.

Joe Harmon_y3pgen

Yeah I figured it out.

Welcome!

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

Quick Links

Find more posts tagged with

jira

workflow

property