Issues and multiple branches on different repositories

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?


1 answer

@Marco Galassiwhich repository integration do you use? What's your VCS? What you described is not a standard-out-of-the-box behaviour, afaik.

I use bitbucket and git. I am using the self-hosted versions though, not the cloud ones

Then bitbucket is my suspect. It's from Atlassian and both applications are linked together. This automated transition  could be happen by bitbucket. Can you have a look in the history of that issue? Who performed the "resolve" transition?

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

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 29, 2019 in Jira Software

Transforming Jira Software projects for general project management purposes

...It's true that there are projects in Jira; but they are merely a way to cut off issues, to tell them apart from other sections of work and to apply rules that are specific to that team (the schemes)....

200 views 0 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you