Scriptrunner Behaviour Initialiser Allowed List Field

Justin_ybfxur

Hi all -

I have a Behaviors script that was slightly modified from the user documentation. This essentially looks for an issue type and updates the list of resolution values the user can choose from (and hides the others) when they try to move it to Done status.

import com.atlassian.jira.component.ComponentAccessor
import static com.atlassian.jira.issue.IssueFieldConstants.RESOLUTION
import com.atlassian.jira.issue.MutableIssue
import com.atlassian.jira.issue.Issue

if (issueContext.issueType.name == "Bug") {
def constantsManager = ComponentAccessor.constantsManager
def allowedResolutions = constantsManager.resolutions.findAll {
it.name in ["Code Change", "Cannot Reproduce", "Will Not Do]
}

getFieldById(RESOLUTION).setFieldOptions(allowedResolutions)
}

My only issue with this is that it currently sets a default value vs. forces the user to select from the list (Please select...). Is this possible? From my research it ignores values entered that don't exist in the system. Thank you

 

 

Carmen Creswell [Adaptavist]

Hi Justin! 

So, since you have restricted the values that can show up in the "Resolutions," the "Please select..." no longer shows up there. There is a (kind of hacky) way to get around this. You can add a new Resolution called "None" at the top of your Resolutions and allow it to show up as one of the restricted values in the code that you put here (just add it to the list you have already). Then, you can add a Validator (Workflows -> 'Edit' on the correct workflow -> 'Resolve issue' transition -> Validator) that checks that one of the proper values has been selected as a resolution. You'll want to use a Simple Scripted Validator and put this in the Condition box: 

issue.resolutionObject.name != "None"

Hypothetically, you could name your resolution "Please select...," but that would likely cause more confusion, especially if you have projects that don't use the Behaviour that restricts the selection options.