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

Help on a Behaviour (ScriptRunner) - Edit screen issue

support for vo

Hello Atlassian Community,

First of all, best wishes for 2023 !
I'm contacting you as we are facing an issue on our Behaviours (ScriptRunner plugin), especially on Edit screen.

Here is our usecase :
We have 2 projects : Project A with Epic issuetype and Project B with Timesheet Log issuetype, with same fields on both.

For these 2 projects, 2 Behaviours created : one for Project A and one for Project B.
Depending on values chosen one some fields, other fields are displayed or not, with default value or not, mandatory or not (->a lot of IF conditions).

To avoid mistakes on Create screens some values are initialized to "None" or "null" by default on some fields.
It's OK for Create screen but not on Edit one : in this case, as we reset most of the values to "None" or "null", the Edit screen resets automatically the values, which we do not want.

So here is our question : is it possible to restrict Behaviours only to Create screen, to avoid it apply on the Edit one ?

Thank you for any help on that case

Accepted answers

Florian Bonniec

Hi @support for vo

There is 2 way to do it.

You can select a Guide Workflow in the Rule Behaviour configuration then for each Fields you can add a condition to execute only when it's a certain action suche as Create.

You can also in you script add the following condition at the begining of your script.

if(getActionName() == "Create"){

}

Regards

All comments

Florian Bonniec

Hi @support for vo

There is 2 way to do it.

You can select a Guide Workflow in the Rule Behaviour configuration then for each Fields you can add a condition to execute only when it's a certain action suche as Create.