Issue Summary

When executing an operation on automation rules, the store creates a new connection to the database and then commits it. This can be a problem as all changes made by a plugin could be  performed in a single transaction. If the plugin relies on this transaction to rollback any uncommitted changes in case of an error, the connection created by AutomationConfigStore is committed outside of plugins’s transaction and there is no way to rollback the changes made by it.
Currently, the way Automation for Jira executes its transactions can be a blocker for some development goals  The suggestion is to change the logic in AutomationConfigStore to support nested transactions. The goal is to be able to rollback all changes made by AutomationConfigStore in a transaction.

Expected Results

Rollback all changes made by AutomationConfigStore in a transaction.

Actual Results

N/A

Workaround

Required, if there is no workaround please state:
Currently there is no known workaround for this behavior. A workaround will be added here when available