Initialize field-values depending on the value of a cascading select field

[Marc Weiland]

Hi,

I have a use-case where I am not sure if this can be done in Jira.

We have a cascading multi select field that is visible and editable in the Create-screen.

The idea now is to set the assignee according to the selection made in the cascading field and to see the new assignee in the form before the issue is created.

I know how to set the assignee after an issue is ceated, that will be the backup solution.

I tried to achieve this with scriptrunner and a behavior, but I have not found a solution yet.

Maybe anyone on here has an idea?

Thank you for your time.

[Marc Minten (EVS) · Accepted solution]

I think this is perfectly feasible with behavior (scriptrunner).

What do you mean with a "cascading" multi-select field ? How is it cascading ?

You say you tried with a behavior, but found no solution yet. What is your problem ? What doesn't work ?

[Marc Weiland]

This is the create-screen:

Now, I want the field assignee to change according to the value of the field Multi_Cascade and I want to see the changes in this screen, before I click Create. I tried with a behavior and the Initializer, this does only work if the field Multi_Cascade is set prior to opening the create screen, but does not update the assignee for further changes on the field Multi_Cascade. Maybe a behavior is the right tool for this and I am missing something.

[Marc Minten (EVS)]

Ok, I see. Your multi-cascade custom field comes from another add-on vendor ?

Can you select it as "Field" in a Behavior definition ?

If no, you probably cannot use Behaviors for this. That add-on is not probably compatible with scriptrunner ?

[Marc Weiland]

Yes, it is from another vendor. They have some examples in the documentatiom regarding scriptrunner, and it seems to work a little different than a standard field. The multi-cascade does not return the selected value but it returns a code for the selected entry, for example, the selection in the screenshot does not return "Option 1 - Level 2_1 - Level 3_1 - Level 4_1" but the code "10101 - 10102 - 10103 -10104". This means I have to implement some sort of mapping here.

The funny part is that the multi-cascade returns the string "Option 1 - Level 2_1 - Level 3_1 - Level 4_1" when accessed via the ComponentAccessor.getCustomFieldManager().

I guess I´ll have to work with the codes for now. Thank you for your time.

[Joe Pitt]

I believe you can do it with a listener. I haven't used one, but your request is similar to others I've seen where a listener was needed. Because the field is a multi-select the options will be very complicated.