Scriptrunner behaviour opening edit rather than displaying dropdown

[Sam Thornton]

Hello!

Been scratching my head over this for a while now, and I haven't been successful at Googling the issue.

I've created a behaviour in scriptrunner using the dynamic select script as a template: https://www.scriptrunnerhq.com/help/example-scripts/dynamic-select-onPrem

I've added my script as part of the field, and not within the initialiser.

However, now when the behaviour is enabled, instead of allowing me to click the select list dropdown within the ticket like I could before, it opens the edit ticket screen instead.

Does someone know how I can stop the edit ticket screen from popping up whenever I wish to change the first select list value, please?

Many thanks!

[Ram Kumar Aravindakshan _Adaptavist_]

Hi @Sam Thornton 

In your description, you mention:-

I've added my script as part of the field, and not within the initialiser.

This implies that you have created a Server-Side Behaviour for the specific Single-Select List.

When Server-Side Behaviour is added, whenever you try to edit the option of the Single-Select List, the Editor screen will be display. This is an expected Behaviour and not a Bug.

Even if you just add the Server-Side Behaviour configuration for the Single-Select Field without any code in it, the moment you try to select an option from the Single-Select Field, the editor screen will appear.

I hope this helps to clarify your doubt.

Thank you and Kind regards,
Ram

[Marc -Devoteam-]

Hi @Sam Thornton 

As I can see and tell on using the same features on an instance, this looks as expected behaviour.

I do think it relates to using a behaviour as fields not using a behaviour can be edited inline.

So it might be worth contacting Adaptavist (Scriptrunner) support on this. 

But I think this is based on how the app works with the options in Jira

[Sam Thornton]

Hey @Marc -Devoteam- 

Ah, I suspected as much. Thank you for confirming that :)

I've got a ticket open with Adaptavist now, and will update here if there are any workarounds.