Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,362,314
Community Members
 
Community Events
168
Community Groups

ScriptRunner Behavior for set Default Value Bug

Edited

Every script I try to set a default value turns the field into an un-editable field, as the default has become a permanent selection and will not let the user change it. We are using SR 5.6.15.1-p5 in Jira Data Center 8.5.3. Has anyone else ran into this problem? Just wondering if this is this a bug or a script error? 

 

Both these scripts set the default, but then the field section can not be changes. 

Example 1 - https://library.adaptavist.com/entity/set-a-default-option-on-a-select-list

Example 2- https://scriptrunner.adaptavist.com/latest/jira/recipes/behaviours/setting-default-fields.html#_setting_defaults_for_selects_etc

 

1 answer

1 accepted

0 votes
Answer accepted

Hi there,

For example 1, you would need to implement the scripts on the initialiser instead of server-side script.

Since the server-side script will run the script every time you want to make changes on the select list hence the behaviour that you are seeing.

Regard,

Amirul

That makes perfect sense, thank you for pointing that out. I will give it another try using the initializer instead. 

 

@Amirul _Adaptavist_ That worked and now it can be changed from the default, but now there is a new problem. After the field value is changed from the default and you go back in to edit any field, the default is pre-populated, instead of showing what was selected. Once you save, it changes the field, so there is no way to keep your selection if changed from the default. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events