Automation triggered but should not

[David Fanjkutić]

Automation rule triggered when I transitioned a bug from Dev in progress to Open. But it should not have been triggered.

Logic is to check if 2 fields changed and those have not changed. Other rules also do not seem to change those fields and also the "Allow rule trigger" is not selected, so I do not see why the triggering happened, it looks like a bug in jira cloud.

See files attached.

[John Funk · Accepted solution]

Hi David,

Can you share the audit log for when the rule ran? 

[David Fanjkutić]

hi John, audit log screenshot atached
 

[John Funk]

Can you share the full audit log please? 

Also, can you share the History of the issue for the time period when the rule ran? 

[David Fanjkutić]

Do you need me to export the audit log ? I am not an admin, I would need to raise an internal ticket to get the export. Or do you think screenshots like the following suffice? Attached audit log of all rules that ran at that time.
NOTE: not all of these ran for the same jira - I transitioned 3 jiras one after the other and the problem happened to all of them - below you see rules that ran on all 3 of those jiras.





issue history attached:

[John Funk]

Sorry, your original image actually shows the full details, it was just out of order for what I was expecting - not sure what that happens as I have seen that before. 

So on to the real issue. I see that the Original Estimate was updated. I think that is what triggered your rule and there is some type of overlap between Story Points and Original Estimate (which to be honest I don't fully understand). 

I suspect there is another rule that is firing on the transition that updates those fields. But it really doesn't make sense that this rule should fire if the Allow rule trigger box is not checked. 

[David Fanjkutić]

They are not out of order, they are ordered by "newest first" :)

If you look at the rules that ran, all have NO ACTIONS PERFORMED. The only rule that performed actions is the one I am here reporting the problem of triggering. I transitioned 3 jiras that is why you see it ran 3 times.
So, no other rules did anything to the fields according to rule audit logs. And even if they did, the box "Allow rule trigger" is unselected.

The Original Estimate and Remaining Estimate got updated by this rule that should not have been triggered. I do not see anything that indicates a problem with my configuration - this is as far as I can see a bug in Jira cloud.

[John Funk]

No, I was referring to the rule audit log - the condition is at the top of the rule but shown as the list step in the audit log. 

The No Actions Performed is because they didn't meet the Condition in your rule, but because this issue has a problem and the others don't. 

I would open a support ticket with Atlassian to see why the rule was triggered. Please post back here with their response so other readers will not the result. 

https://support.atlassian.com/contact/#/

Good luck!

[David Fanjkutić]

it turned out to be a workflow configuration issue in our instance, so it was not a bug in Jira.

[John Funk]

Very good - thanks for the update!