ScriptRunner Behaviors not working in edit mode of the issue

[Madhuritha Ankathi]

Hi Everyone ,

Following our migration from Jira Data Center to Jira Cloud, we updated the behaviour scripts. We’ve observed that the field behaviours are working correctly in the Create form, but they are not applying in the Edit view of issues.

We have already ensured that the behaviour is mapped to the appropriate view types (“Create, Transition, View/Edit”). Interestingly, the same script works as expected in our test Cloud instance, but not in production.

Example of the problem:
When selecting the Business Unit field (e.g., FPG, Global Team), the behaviour should make the BU Subteam field visible and populate it with the corresponding values (e.g., FPG X, FPG Y, FPG Z). This works correctly on the Create screen.

However, on the Edit view, the same behaviour does not apply — the BU Subteam field remains unaffected. In fact, several of our behaviours are not functioning on the Edit view, even though we have mapped them to “Create, Transition, View/Edit.”

Looking for a solution , Thanks !!

[Wajdi from VIP_LEAN Solutions]

Hello @Madhuritha Ankathi 

Due to our experience with UI modifications (which are core capabilities of Atlassian and the foundation of every behaviour app, including ours), there are differences in support. The UI modifications (= Behaviours) do not have consistent support across the board. Here is the list of dimensions involved:

- Jira or JSM

- Field Type

- Screen Type

- Project Type

See also Atlassian docs:

https://developer.atlassian.com/platform/forge/apis-reference/jira-api-bridge/uiModifications/?tabId=1&tab=jira#supported-fields-per-view

https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-ui-modifications/?tabId=3&tab=jira+global+issue+create#view-specific-requirements-and-limitations

I assume Adaptavist has corresponding documentation reflecting the support level at theier app level. 

Best, Wajdi

[Arkadiusz Wroblewski]

Hello @Madhuritha Ankathi 

Just a few questions to help me and others help you out.

1. Is the production project Jira Software, or JSM?

2. Is it company-managed or team-managed?

3. Is the affected field type supported on Issue View / View/Edit?

4. Is the method you use supported on Issue View, for example setVisible, setValue, setOptionsVisibility, etc.?

5. Does the behaviour log show that the behaviour actually ran in production?

Cloud version ScriptRunner are different from Data Center and don't allow as much background manipulation. Therefore, function parity shouldn't be expected.

For deep troubleshooting, Adaptsvist will of course be most helpful.