I tried using Jira smart commits on our Jira+Bitbucket setup, trying to get it to resolve issues once fixes are pushed.
The problem is that once the commit is pushed to a side branch (not master, since it is important to run a CI pipeline on it first) -- the issue gets resolved immediately.
This is a rather strange default behavior, as all other implementations for automatic issue closing I've seen only perform the action once the commit hits a "finalized" branch -- otherwise one would be exposed to the possibility of forgetting to merge or removing the change altogether...
Is there a way around this behavior? Can I make the smart commit action(s) apply only when the fix lands in a certain branch?
I believe you can find answer in this topics
Hope, this is helps you
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
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