Scenario: rule triggers without leaving an entry in the audit log?

[Zvonko Podbojec]

Hi everyone,

Loving the addon, it immensely helps us in our daily workflow :)

Today I've encountered a strange situation - two rules which are scheduled to run on a cron-defined schedule seemed to have triggered themselves. I checked the audit log, and there is no entry in there for the executions. Additionally, from the looks of it, the datasets they processed were just the diffs from the previous execution, instead of full datasets.

The rules are Scheduled JQL searches (bulk process), and the results from it are then sent to Slack (e.g. we have X issues in status Y).

Any idea why this might have happened?

Kind regards,

Zvonko Podbojec

[Nick Menere]

Hey Zvonko,

Great to hear you are enjoying Automation.

In terms of the rules only executing a "diff" this can be explained if you have the option for "Only include issues that have changed since the rule was last executed":

 

Simply unchecking that will result in all issues being picked up.

In terms of the rule executing outside of schedule, this is very bizarre and not something I have heard of before, esp. if there is no record in the audit log. (We are very strict about writing every execution to the audit log). The only explanation I can think of is that there is another rule configured that ran. If you raise a support request I can help you track this down and get to the bottom of it - https://codebarrel.atlassian.net/servicedesk/customer/portal/1

Cheers,

Nick Menere [Code Barrel - Automation for Jira]
Co-Founder

[Nick Menere]

Update:

We worked through this issue in Support and there was a test server that made it look like the prod server was running extra schedules.