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 ?
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.
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...
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.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs