Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,365,374
Community Members
 
Community Events
168
Community Groups

Automation: Applicable Conditions Failing

Edited

As part of on automation rule using subtask closure as a trigger, a condition exists related to parent issue type. For instance, if the subtask is of a Quality Control type and the parent is of a User Setup type, then the actions should fire. I have seen several instances of this logic breaking for reasons I'm unable to determine, to the point where seemingly identical situations will have different results. 

Specifics of the rule:

JiraQCAutomationRule.png

I have validated the JQL and confirmed that the parent of a subtask is included, but see that the audit log claims the condition was not met. I confirm that the parent issues have never changed issue type. The rule appears to fail in this manner more often than it succeeds, but it does do both. Has anyone experienced anything similar

2 answers

1 accepted

2 votes
Answer accepted
Fabian Lim Community Leader May 11, 2021

Hi Matt,

I would recommend the following changes:

automation.png

Change the issue types to the ones you need.

Thank you Fabian, this solved my problem! Placing the issue type check inside the related issues block has worked in each case I have tested!

Like John Funk likes this
0 votes
Mykenna Cepek Community Leader May 11, 2021

Maybe you've done this already, but the first thing I would do is litter your rule with "Audit Log" actions, in order to validate the issues and fields as the rule progresses during each execution. For example:

  • Between the Trigger and the Conditional, log the (trigger) issue key and type, as well as the parent issue key and type.
  • Immediately after the Conditional, log that the conditional succeeded: "Got here"
  • Before the transition, log the issue key and intended action: "Transitioning {{issue.key}} to W4A"
  • After the transition, log that you got past the Transition

Then set up for a test and run the rule. Does the output in the Audit Log exactly match your expectations? Sometimes you'll see things you don't expect, and can then fix your rule.

Otherwise, if the problem persists, you have a lot of info for Atlassian Support to report a bug. Be sure to grant them access to your instance, and provide clear steps for them to reproduce in your instance (how to set up for the test, the rule name to run, to look in the Audit Log to verify issue fields as the rule executes, and what you expect to happen).

Thank you Mykenna, I'll try implementing a few of those log actions and see what they reveal. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events