Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Manual Rule Using JQL Does Not Include Trigger Issue

Simon Brooke February 13, 2018

Hi Team,

So I have a manual rule that generates a report for change management...

The rule uses branched/linked to execute JQL to gather up the issues for the report...

HOWEVER, if the issue from which the manual rule is invoked would have been included in the JQL results, it is NOT passed through to the actions so does NOT appear on my report...

In the audit log I can clearly see that the trigger issue is removed from the issues list...

I can sort of imagine this may be due to issues with recursion or similar fouling up the rule execution...is there any way around this?

 

Thanks,

Simon

1 answer

1 accepted

0 votes
Answer accepted
Deleted user February 13, 2018

Hey there Simon,

Yeah the trigger issues doesn't appear in the "Related issues" branch so they don't get double processed. You can explicitly reference the triggering issue from the branch by using the smart value {{triggerIssue}} (see https://docs.codebarrel.io/automation/smart-fields/smart-fields.html)

If you need to perform a bunch of actions on the triggering issue, then you can also add a new branch on the "Current issue" to perform actions on them

Cheers,

Mark C

Simon Brooke February 14, 2018

Many thanks Mark

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events