Initial branch in Jira is inconsistent with Pull Request

Question

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.

Dario B · Answer

Hello @rsbeckerca ,

In this case then you might still be interested in the 2 Feature Requests linked to it:

*  JSWCLOUD-13411 Show target branch on pull request dialog
* JSWCLOUD-20711 Workflow Trigger to merge a pull request into a specific branch

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

rsbeckerca · Answer

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.

Dario B · Answer

Hello @rsbeckerca ,

If I understand correctly what you are writing, the issue here is that:

* Branch A is created from master (main branch).
* Branch B is created from branch A.
* In Jira, when you click on 'create pull request' on branch B, the default option is to merge to master instead of merging to branch A

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:

* JSWCLOUD-17862 - Creating branch and creating on pull request from development panel will choose the branch option as a default branch

In case my understanding is not correct and/or you are actually reporting something else, please provide more details.

Cheers,
Dario