Issue Summary

Currently when there is a loop detected it only indicates that the rule execution was prevented/stopped as it detected a loop but it doesn't display any information on which specific work item id did the loop detection occurred. 

Steps to Reproduce

1. Login into Jira 
2. Create 11 automation rules that trigger based on the Jira.trigger.issue event
3. Now notice that when you perform the action such that all 11 rules execute the 11 automation rule executing will be marked as a loop and that execution would be prevented. 

Expected Results

There should be information around which ticket caused the Loop and that should help with understanding further what to adjust in the automation rule.

Actual Results

Currently in the automation rule audit log it displays "Loop" "Rule execution was stopped since an execution loop was detected. Please check *all your rules and disable the 'Allow rule trigger' setting in 'Rule details' where it is not needed. We stopped execution after detecting a long chain of rules triggering other rules. Chain length:*
10" however this doesn't help in understanding what caused it.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available