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,370,042
Community Members
 
Community Events
168
Community Groups

Related issue condition executing when it should not

Hello,

I have a global automation rule that affects 2 projects. The rule is triggered by updated to the Fix version(s) field in one project (DPM). When that field is updated I want to have a new ticket created as a child of the triggering issue. The child ticket should be created in the second project (HIX). The new child HIX ticket should only be created if there is not already an existing child HIX ticket. Everything seems to be working fine with the rule except when I try to check for a pre-existing child HIX ticket. 

Below are the conditions I have under an if block, I only want the child HIX ticket to be created if all these conditions are met. The expanded condition is where I am checking for the presence of an existing child HIX ticket. It seems like this should be pretty straightforward but when I test the rule even if there is an existing child HIX ticket a new one is still being created so somehow my check below is not working.

Any help is appreciated.

 

image.png

1 answer

Hello Atlassian team, any help with this issue would be appreciated.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events