One of the behaviors I discovered in looking at this is when an issue is manually transitioned (so it is already in the destination status).
I added a condition to verify the current status is expected. For example, in TO DO before automatically transitioning to IN PROGRESS when a branch is created.
ENHANCEMENT REQUEST for the TRANSITION rule:
Built-in automation check should be if the issue is already in the DESTINATION status, just don't fire like some of the other built-in automation rules. The audit log should show "issue already transitioned" or something similar.
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events