When we create a branch in Jira, the branch is always based on our current Sprint branch, which in turn is based on our main branch. When we create a Pull Request from Jira, the software always uses the main branch instead of the origin branch on which we based the ticket branch. This is causing confusion, errors, and a whole bunch of rejected Pull Requests. Jira should be able to set up the Pull Request properly based on the original branch that was specified.
Hello @rsbeckerca ,
If I understand correctly what you are writing, the issue here is that:
Is this correct?
If this is correct then can you kindly let us know what are you using for source code management?
I am asking because when Jira is integrated with Bitbucket Cloud you can actually change the source and destination branches for the pull requests you are creating from Jira, since this is actually just redirecting you to Bitbucket as shown in below screenshots:
However, in case you are using Bitbucket Cloud and what written above applies, you might be referring to the behavior specified in below bug that was closed without being fixed since it didn't manage to get much traction:
In case my understanding is not correct and/or you are actually reporting something else, please provide more details.
Cheers,
Dario
I am using Jira and BitBucket Cloud for this, but did not see the JSW-CLOUD-17862 issue before it was closed or I would have commented in favour of it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @rsbeckerca ,
In this case then you might still be interested in the 2 Feature Requests linked to it:
You may want to vote and watch the above feature requests so that you will get notified in case of any update. The feature will be addressed according to the Implementation of New Features Policy.
Cheers,
Dario
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.