Issue Summary

This appears to only happen with the field "Parent", but if you create an automation with "Field value changed" as the trigger and select the "Parent" field without specifying which event to listen for, the automation will always double trigger upon creating an issue in which the parent is set during the issue creation screen.

This seems to be because creating an issue with a parent listed will fire off both a "Issue created" event, and "issue updated" event, both of which trigger the automation.

Steps to Reproduce

1. Ensure a "create issue" screen has the parent field
2. Create an automation with the "Field value changed" trigger. Set the field to parent, don't specify a specific event action. Add any log action message, can leave this blank.
3. Create a new issue and add any other issue as the parent during the issue creation screen itself.
4. Go and view the audit log and see that the automation will trigger twice when that issue was created.

Expected Results

Automation should only trigger once since the field value for the parent would have only changed once (during creation).

Actual Results

Automation triggers twice.

The below exception is thrown in the xxxxxxx.log file:

...

Workaround

Specify which issue action (create, edit, etc.,) if possible.