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

Apply Script to user editable field

David Doria

Is it possible to make a 'Select List (multiple choices)' field that a user can interact with but is also controlled by a script? For example, I want a parent issue to "inherit" the selections of a field of its children if it has any, but if it does not, then allow the user be able to edit the field as normal.

I looked at Behaviors, but those appear to apply only on "Screens". I have a constraint that I also want this field to be "live" in Structure, where there is no such "Screen" on which the Behavior would apply.

Is this possible?

Thanks,

David

Accepted answers

PD Sheehan

Hi David

Unless there is some other custom field from the marketplace that supports dynamic lookup based on other issue attributes you can't achieve this with standard fields using Scriptrunner but not within the confines of what is supported by Behaviours.

The solution that comes to mind involves the Select List Conversion. But this would render the field as a regular text field while using Structures.

All comments

PD Sheehan

Hi David

The solution that comes to mind involves the Select List Conversion. But this would render the field as a regular text field while using Structures.

David Doria

Hi Peter-Dave,

It's ok for Structure to render regular text.

I'm not sure which part of Select List Conversion I should be looking at?

Do I start with a usual (non-script) MultiSelect Custom Field? I see a function 'convertToMultiSelect' - what would I need to convert TO a MutliSelect if I already have the field as a MultiSelect?

David

PD Sheehan

You have 2 choices.

1) Use the existing Multi-Select field. Continue to maintain the overall list of values (options) in the Custom Field context admin screen. In which case, you won't use the Select List Conversion, but instead, we will use the "setFieldOption()" method to dynamically show/hide some of the options (the option must first exist in the custom field config).

In structure, when attempting to do in-line edits, you will still get the full list.

2) Using Select List Conversion, you would first create a new custom field that you want to act like a multi-select. It has to be a regular text input field.
In a behaviour script, you would then either hard code the list of values you want to allow (with some logic of which values to display or not) or build a separate custom REST Endpoint script to load those values from some other data source (those values can then be stored elsewhere and managed without needed jira admin access).

In structure, when attempting to do in-line edits, you will get a text field that users can modify without validation.

David Doria

Option 1 sounds great, except I don't understand where to put the code. It's not a Script Field, so there's no 'Inline script' to control the field. And it can't be a Behavior, because that doesn't get executed by Structure. I must be missing your point?

Welcome!

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

Quick Links

Find more posts tagged with

scriptrunner

adaptavist