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.
The Jira Service Desk marketing team is working on a guide to help new Atlassian customers switch from email to JSD and we'd love to hear from you! Please share: - What made you realize that i...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs