Automation Condition not working - a bug?

[Evaldas]

Hello everyone. I don't understand - what am I missing or why the "Related issues condition" doesn't work?

A simple Automation: when an Issue is transitioned to "In Progress" in one project, check related issues (that are "caused by" this issue) and if they are in "Sent", then transition them to "In Progress" as well.

* As my Issues are linked between 2 different Projects, so yes, the Automation Scope is Multiple-projects (the proper ones :) ).

* Workflows are aligned (you can transition from "Sent" to "In progress")

* Upon debugging, I added a simple "Issue field" condition with Audit log action and the related Issue is FOUND and with status "Sent":

* Event the problematic "Related issues condition" with "Matching JQL" finds that related Issue:

SO WHY it doesn't pass in Automation and doesn't do next action??

And yes, if I change condition to "Issue field" condition, automation works fine:

But I want to understand what I am missing with that "Related issues condition"

[Mark Higgins]

Hi @Evaldas,

It could be as a result that automation cache the information at the start, and if you edit something, then you need to refetch the data?

https://support.atlassian.com/automation/kb/usage-of-refetch-component/

It doesn't look like you are editing, however may be worth a look.

Mark

[Evaldas]

Hi, @Mark Higgins , I've changed that Automation to use "Issue field" condition (as I've wrote above), so I don't want to rechange and retest, however, I'm not doing any editing on the related issue that I'm checking, so refetching doesn't seem as needed... and what's more - the "v2" automation differs from v1 only with that condition type and works without refetching.. so it must be smth with that "Related issues condition"..