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

ScriptRunner Behaviour not working on Create on specific Jira projects (PORTAL ONLY)

Harvey Bennett_iw6htm

We have a situation where the Behaviour feature offered by ScriptRunner is not working on specific Jira projects. Changing field visibility, editability, and code that changes these features do not work on the project. I can see code executing those through the initializer when i launch our JSM portal screens that the behavior is tied to in the jira.log file but the 'interactive' part of it is non responsive. I have cloned the Jira project and strangely enough once the behavior is applied to that Jira project is works. Is there any plugins or configurations that have been known to impact or override the usage of Behaviours?

Thanks,

Harvey

Accepted answers

PD Sheehan

Could your project context fall into more than one behavior mappings?

Check for "All Projects" or "All Request Types" in addition to any that are specific to your project/request type.

When you have more than one behaviour mapping and both touch the same field, there is no guarantee of which one will win.

If that's the case, you need to either adjust the mappings or combine the two sets of rules into a single one that will have some logic to know which to apply/when

If all else fails, disable all but the one behaviour configuration you are interested in to see if it will work.

All comments

PD Sheehan

Could your project context fall into more than one behavior mappings?

Check for "All Projects" or "All Request Types" in addition to any that are specific to your project/request type.

When you have more than one behaviour mapping and both touch the same field, there is no guarantee of which one will win.

If that's the case, you need to either adjust the mappings or combine the two sets of rules into a single one that will have some logic to know which to apply/when

If all else fails, disable all but the one behaviour configuration you are interested in to see if it will work.

Sachin Dhamale_o1c5zi

@Harvey Bennett

To find out which app is causing this issue is put jira in safe mode ( disable all plugin except script runner) and check if its working fine or not.

If you are still facing this issue then its related with some configuration.

Harvey Bennett_iw6htm

This appeared to be my issue even though different fields are present throughout the behaviours. I suppose it is smart to look at the plugin itself before ruling it out and blaming other plugins. Thanks for the suggestion and answer.

Harvey Bennett_iw6htm

This was my 2nd option that I was planning on exercising. I didn't need to go down this route but always helpful nevertheless. Thanks for the suggestion.

PRAMOD KUMAR REDDY KASIREDDY

Question :

We're Using An Behaviour for (Check Commit Values) Script. in a test A project. there we have kept conditions like 1) When Workflow Action: Fix(transition). it is working perfectly. Here we are using the Production A Project. Same workflow and same fields everything is the same. But when we mapped this project to Behaviour. the script Validation working is in every transition. not only in Fix Transition. At the same time in Test A Project, this behaviour works fine.

Ranchin Hervé_zb1pk9

I have a trouble similar but i found that the behaviour run correctly for a user who is NOT in a organisation !
Have you any idea what are the link between Organisation and script ?

For information the script only add text in the description !

Welcome!

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

Quick Links

Find more posts tagged with

server

scriptrunner

jira-software

jira-software-server

behaviours

jira-service-management