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

rules - How to sequence, how to terminate

Rick.Piovesan

I have a set of automation rules:
1) that need to run in a priority sequence. That is, a given ticket could match on a number of rules so the most important one should go first. How to do this?
2) once a rule has been matched, how to abort further rules from processing?
RickP.

Accepted answers

Dirk Ronsmans

Hey @Rick.Piovesan and welcome to the community,

Unfortunately there is sequence possible in the execution of Automation rules.

When the rules all match they will all fire at the same time (or in a random order which you cannot control).

The only way to create what you want would be to create a single rule and within the rule define the multiple scenario's. I dont know your use case of course but it will be the only way to give some kind of control to what is executed and when.

Within a single rule, it will run top-down and you can build this up with conditions.

All comments

Dirk Ronsmans

Hey @Rick.Piovesan and welcome to the community,

Unfortunately there is sequence possible in the execution of Automation rules.

When the rules all match they will all fire at the same time (or in a random order which you cannot control).

Within a single rule, it will run top-down and you can build this up with conditions.

Rick.Piovesan

Wow this is unexpectedly crude - a rules engine with no way of threading, prioritizing or aborting (and this is the 'new' rules engine !?!)

I will go with your idea of "One rule to Contain them all" (where have I heard that before..). But its going to be a huge, messy, complex and probably indecypherable mess once I finally get it working.

Big, big, big disappointment in Atlassian ..

Rick.

Dirk Ronsmans

Well you'll have to write out your rule/rules and see if there maybe it a way they can trigger each other if needed.

That could also be a way of linking them together and sequencing them.

I understand that it would be great to have multiple rules with the same trigger and have them run as dependencies of each other.. but nope..

Having multiple massive If's tho will be your best bet for now.. We'll see if they improve it in the future!

Rick.Piovesan

to your first para - how could a rule trigger another rule? If 'A' needs to somehow trigger 'B' but no way to make sure that 'B' doesn't run before 'A' ?

i don't care/want dependencies, just enough to be sure that 'A' runs before 'B' (prioritizing) would be sufficient for now - something that is really basic to any rules processing.

With this alone we can work around all other painful limitations - i.e., "stop processing any more" could be a flag that is checked in each subsequent rule ..

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-management