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

Why are 'no actions taken' for this automation rule?

Melle van Keulen

In our sandbox this automation rule works, in our production environment it doesn't. What could be the explanation for this?

The only difference is that in our sandbox environment the issue is made with the new Forms, in our production environment we use the Proforma add-on. But I don't think that should make any difference.

Accepted answers

Alex Koxaras -Relational-

Hi @Melle van Keulen

Try re-fetching the issue's data before that If statement. From the looks of it, the rule is triggered before any value is entered on that field. That's why no action is taken. Since proforma on the prod level is an app, most likely it could take place AFTER the rule has ran.

All comments

Dirk Ronsmans

Hi @Melle van Keulen ,

At first glance that should be correct and triggering (especially if you mention it works on PROD and not in the sandbox).

Could it be that the value on the "KRC IT Componenten" field was not entered until after the creation of the issue?

Perhaps a look at the history of the issue could reveal that.

Melle van Keulen

It works in the sandbox and doesn't work on PROD. THe value KRC IT Componenten is entered when filling in the form, so not after. This is also seen in the history of the issue.

Dirk Ronsmans

Oh apologies, misread that one.

I do notice that you are entering the value thru a Proforma form so I'm guessing that form has a linked field then to the KRC IT Componenten field?

And that's the exact same way it is set up on both PROD and Sandbox then? (both using proforma as the entry point?)

I would suggest adding some debugging to your automation, for example a "log" action where you output the value of the custom field just to be sure something is in there and it's not returning empty at creation.

I'm not yet fully familiar with the proforma integration and how that would trigger Automation.

Melle van Keulen

It is indeed a linked field to the KRC IT componenten field.

In Sandbox we used the new native Forms and in PROD we still use the ProForma add-on.

Could you elaborate on the debugging, what do you imply?

proforma seems to fill in the field which is linked to it, guessing it should trigger automation because the field was filled in, no matter what, right? Or do I miss something here?