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

Workflow Transition (Condition/Validator) vs. Automation rules

bschmi

Hello!

In case I have a condition/validator in place for a workflow in Jira Service Desk and an Automation Rules that says otherwise - which mechanism of them two take precedence?

Thanks,
Birgit

Comments

Ravi Sagar _Sparxsys_

Hi @bschmi

Can you elaborate your use case?

Workflow condition/validator controls the transition of the issue.

Automation Rules does automation, but it will respect the workflow condition/validator (mostly).

Ravi

bschmi

Sure - let me explain further:

The relevant part of the workflow is:

Waiting for support == cancel request ==> Canceled

The Automation rule reads (please disregard that they do not make any sense from a Business perpective):

WHEN
Comment added
THEN
Transition issue: Cancel request

The workflow has one condition:

Conditions
Only users in group "testgroup" can execute this transition.

==> in this example the executing user is not in this testgroup.

From log of Automation I recognized that there will be logged an error as soon as the Condition is introduced. Before introducing the Automation rule works perfectly!