Issue Summary

When setting up a webhook with JQL filtering with DVCS smart commits enabled causes workflow transitions triggered by commits become corrupted.

Steps to Reproduce

1. Create the DVCS org (e.g. Bitbucket) and a repo inside of it.
2. Connect your org to DVCS plugin in Jira DC, make sure Smart Commits are enabled.
3. Create a Jira user with an email matching the Bitbucket user, so that smart commits can transition the issues (user should have proper permissions).
4. Create TEST project in jira.
5. Create a simple workflow with circular transitions loop:
   
6. Assign the workflow to TEST project. 
7. Create a TEST-1 issue in TEST project.
8. Create a simple webhook reacting to Issue Updated and having some JQL filter:
   
9. Now, add a commit to the repo with a commit msg: "TEST-1 #in-progress"
10. Refresh the repo in DVCS accounts panel - the issue seems to not be reproducible when transition is triggered via webhook call from VCS host to Jira.

Expected Results

Issue is transitioned and issue status in DB state is not corrupted. Statuses in OS_CURRENTSTEP and jiraissue match.

Actual Results

1. Observe the issue is transitioned, but there's this line in logs:

   [c.a.j.util.thread.JiraThreadLocalUtils] Uncommitted database transaction detected.  Closing...
   

2. Issue ends up in the inconsistent state. (OS_CURRENTSTEP table is not updated while jiraissue is.).
   

Workarounds

1. Disable webhooks using JQL filtering, or replace them with A4J rules.
2. Upgrade to Jira 10+, webhooks processing is done async there, and this issue was not observed.