ScriptRunner Behavior can Prevent New Values from Appearing within an Existing Custom Field
要約
This problem is related to a third party plugin, and therefore not supported by Atlassian. See Atlassian Supported Plugins for more information.
In ScriptRunner, Administrators can write custom behaviors in order to manage certain aspects of Jira. In some cases, these behaviors can target a Custom Field in Jira and force only specific field values to load for that field in a given Project, even if new values are added to the Field Configuration later on.
環境
All version of Jira running Scriptrunner
診断
When users try to leverage these values from the: create, edit, view, issues screen in any browser, the newly created options are not available in the project.
In the Browser's web console, you will see the page trying to make an call out to the Behavior in ScriptRunner such as:
Fetch finished loading: POST "https://jira/rest/scriptrunner/behaviors/latest/runvalidator.json"
In the atlassian-jira.log file, you will see data about the ScriptRunner Behavior such as this:
Behaviour_1: <config id="1" name="<behaivor name>" description="<behavior description>" disabled="false" use-validator-plugin="false"><init/><field validator="server" id="customfield_10403" readonly="false" hidden="false" required="false" name="<Field Name"><validator-script><script>import com.onresolve.jira.groovy.user.FieldBehaviours 原因
The behavior in ScriptRunner has been written and designed to only show specific values for the Field within the Project
ソリューション
Update the Behavior to include the new values or Disable the Behavior altogether