Jira smart commits on side branches?

[rotem]

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?

[Yevhen Rohovets]

Hello,

I believe you can find answer in this topics 

https://community.atlassian.com/t5/Jira-questions/How-do-you-set-up-your-Jira-project-for-smart-commits/qaq-p/780749

https://community.atlassian.com/t5/Bitbucket-questions/Transitions-with-Smart-Commits/qaq-p/904266

Hope, this is helps you

[rotem]

That doesn't solve the issue at all, as it doesn't describe how to control which branches trigger the smart actions... Unless I'm missing something?

[Wyatt Mufson]

This does not even attempt to answer the question