Issues and multiple branches on different repositories

Question

Hi, first time here.

I had to face this situation. I have a bug to resolve. I opened a bug issue on Jira. I figured out that, in order to solve an issue, I had to work on 2 different repositories. At this point the issue is in state open.
So, I have created 2 branches (and the issue passed to the in progress state), one per repository, in order to work on the required fixes. At a certain point, I was ready to make pull requests to merge back the branch in the development branch.

I would have expected the issue to enter the resolved state when both the branches would have been merged. But as soon as the first pull request successfully merged, the issue changed to resolved.

What am I doing wrong? Is there a design problem? Can this be configured somehow, like setting the transition to resolve trigger to fire when all the branches from an issue are merged back?

Thanks

manus · Answer

Solved here: https://community.atlassian.com/t5/Jira-questions/Re-How-to-tell-if-there-are-multiple-pull-requests-assoc/qaq-p/1465756/comment-id/440829#M440829

Sebastian Kleinholz · Answer

My guess was right :)  This means you have to configure Bitbucket to take this two branches into account.

I cannot help you further at this point - I have only rudimentary know-how of Bitbucket. But if you cannot "disconfigure" this behaviour, I recommend to switch it off.

marcogalassi · Answer

Yep, the history says "Automated transition triggered when USER X merged pull request #16 in Bitbucket - Yesterday"