JIRA automations - trigger rules based on setting a label of a specific item

[olivier costa]

We have broken up a complex rule in to 32 rules very simple ones, and we want to activate them every night (operational) AND via a manual action (for testing)

The manual action is setting a label on a dedicated item that is only used for this triggering
The scheduling is done by a dedicated scheduled rule that 1st clears the label and then sets it.  

The 32 rules all listen to work-items being updated, but with the condition that it has to be a specific items and that it must have a specific label.  

We introduced this because we currently have the system running with each rule being scheduled (on the same moment) - which works for the operational context, but is very impractical for testing...  

But now we have trouble converting the rules: 

the trigger works (setting the label)
it starts a lookup (works as well - the right items are listed as associated)
but then when we try to loop over the "looked up items" , check some conditions and if all met, transition the "looked-up item".   the system keeps acting on the item that triggered the rule...

see setup and audit feedback in attachment.  

Me nor Grok were able to find a way that works...  
Maybe you know ?  

[Bill Sheboy · Accepted solution]

Hi @olivier costa 

An advanced branch is over data, and not work items.  That is why the rule you show repeatedly acts upon the trigger work item...not the ones found by the lookup results: they only contain the data.

When you want to perform actions and test conditions over a set of work items, please use one of the other branch types, such as a branch on a JQL expression.

Please note well: JQL branches cannot act upon the trigger work item.  And so if you also want that one tested / updated, some additional rule logic is needed.

Kind regards,
Bill

[olivier costa]

Hey @Bill Sheboy  thx for your reply !

Jep the JQL branch did the trick indeed !  

[olivier costa]

So this allows me to both schedule this rule (and its siblings) and run them manually for testing updates ! 

[Bill Sheboy]

Awesome; I am glad to learn that helped!

And just a reminder from my earlier comment: for the rule triggered on Work Item Updated, the trigger one can never be processed by a JQL branch.  That is, branch on JQL automagically excludes the trigger by adding to the JQL

... AND key != {{triggerIssue.key}}

When you also need to process the trigger, it must be done separately from the branch.