Why Script runner behavior of listner wont work in Jira policy type project

[PLaksh11]

Hello,

We are using "Jira-Business project" and found Script runner Behaviors and listeners are not working in edit screen of a ticket.

Earlier we used "Jira-Software project" and there behavior and listeners are working.

Is there any reason why Script runner is not working in "Business Projects".

Note: We want to Hide some custom fields based on other custom field value in Jira Business Project. Please let us know is there any way that i can achieve this.

Thanks,

Prathap DL

[Arkadiusz Wroblewski]

Hello @PLaksh11 

- Are you trying to solve this with a Behaviour or with a Listener?

- What exactly should happen: hide/show a field on screen, or update something after the issue is created/edited?

- On which view are you testing it: Create, Issue view/Edit, or Transition?

- Which field are you trying to control?

- Is that field a standard Jira field or a custom field?

- Is this a company-managed project or a team-managed one?

- Do you have the ScriptRunner Behaviours companion app installed?

- Does a very simple Behaviour work in the same project and issue type?

I am asking because on Cloud, Behaviours are limited to supported fields/views and require the separate companion app, while Listeners are a different feature entirely and run on Jira events rather than changing the UI directly.

[PLaksh11]

Hi @Arkadiusz Wroblewski  

Thanks for the response.

1. Script runner is installed and we are using for Jira software projects.
2. Its an Company-manages projects.
3. Behavior will work only in create screen.(For business company managed project)

You can check the updates from script runner website.

Note: We need to Hide/Show fields(custom fields) based on other field value(Custom field) in Edit/View Screen.

Based on workflow transition and field value update for both we need behavior to work.

[Arkadiusz Wroblewski]

@PLaksh11 

What you found matches the current ScriptRunner Cloud limitation.

For Business company-managed projects, Behaviours are currently supported only on the Create view, so I would not expect the same hide/show logic to work on Edit / Issue View there. And for the Listener part, that is a different feature anyway, because listeners react to Jira events in the background, they do not control field visibility on the screen.

So from what you described, this does not look like your script is wrong. It´s a product limitation for that project type in Cloud.

At this point you should raise it directly with Adaptavist support. They should be able to confirm whether there is any supported workaround for your exact case, or whether this is simply not possible today on Business company-managed projects. That is probably the fastest way to avoid spending more time troubleshooting something that is limited by design.