We seem to have experienced multiple times where an Automation Rule (JIRA Service Desk) have executed while examining the history of affected issues should have had the IF-statements yield `false` but somehow the rule is executed anyways.
Have anybody else experienced something like this before, because we have not been ableto pinpoint why this happened even though it shouldn't have?
We're running JIRA Service Desk 3.4.0 on a JIRA server instance.
Hello Community 👋, I'm a product manager at Atlassian, looking at improving change management capabilities across our products. In particular, we're looking at bridging the gap between Dev & ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event