it will be very helpful for developers to have this "Create Branch" feature available in Jira for Gitlab

But not so great for Atlassian trying to persuade people to use (purchase) Bitbucket Data Center, rather than a direct competitor such as GitLab or GitHub.

Is there a plan to use this feature for Gitlab as well? Gitlab is getting quite popular and it will be very helpful for developers to have this "Create Branch" feature available in Jira for Gitlab?

+1

+1

+1 Please listen to your community, this feature could really help out for a lot of users

+1 we use both. Bitbucket and GitHub. It should work similiar.

Very disappointed to find out this is a Bitbucket-only feature. The Atlassian Product Manager who is preventing this from happening needs to rethink strategy. Stop trying to pit Bitbucket against GitHub - you will lose!

+1

Hello liveordevtrying1497589170,

That sounds interesting, do you mind copying the link to it here? The only thing I found that handles branch creation is this app https://marketplace.atlassian.com/plugins/com.osowskit.jira.github.app/cloud/overview

and it's free, but it apparently does only that, none of the other integration features.
Is this the one you are referring to? Thanks for your suggestion!

There is an add-on called 'Github Integration' on the store that has a new feature that does just this.  Its only $10.

+1   It would be great to have "Create Branch" work for GitHub.  Please reopen. 

+1

Disheartening to see Atlassian act in such a childish manner. Acting this way reinforces Atlassian's lack of confidence in their own products. More reason to not use Atlassian tools. 

This issue is closed because of Atlassian's cynical marketing. The 'Create Branch' feature is supported for Bitbucket but not Github, because Atlassian want you to use Bitbucket. They have no incentive to give you a reason to choose Github. It's the Apple approach - lock everyone into a closed system so no one can ever leave.

Why is this issue closed?  This is an active and current issue as of 2/27/2018.

At least tell your customers why you will not pursue this feature. Please?!

+1 please add this feature

+1 this needs to be reopened. It's a great feature that helps to track properly

+1 please add this functionality to Jira

Why is this issue closed?  Atlassian has a magnificent talent for creating ill-will with their users by not fixing issues like this.

+1 Please reopen

+1 please reopen

+1 this needs to be reopened

+1 Very useful feature

+1 I would benefit from this feature as an Atlassian cloud customer who uses Github for SCM.

+1 This needs to be reopened.

+1   It would be great to have "Create Branch" work for GitHub.  Please reopen. 

+1 for this feature, please re-open.

This should be re-opened.  The "answer" provided JRASERVER-35175 is insufficient, as the trigger from pushing new branch > github which gets picked up by the JIRA webhook is not what is being questioned.  The request is for giving the same functionality to create a branch in Jira, which is offered to Bitbucket only.

+1

**Turns out that the Branch Created trigger does work, I can create a new branch with the JIRA issue ID in the name, push it up to github, and it will run any workflow transitions that I've setup for it. Maybe the original intent of this issue was to request "Create Branch" functionality where you can automatically create a new branch in your github repo from the JIRA issue.

+1

you are only providing 6 triggers for GitHub, make them work at least!

What do you mean with "Won't Fix"? Nobody will switch to Bitbucket for this. Higher chance that people will leave JIRA, just sayin'...

+1

And it would be nice to vote on this properly.

It is a sorely needed feature ...

+1. I will not be forced to switch to Bitbucket. 

I agree... documentation needs to be updated. For me, this was:

https://confluence.atlassian.com/adminjiraserver070/integrating-with-development-tools-776637096.html

Why was this issue resolved as "Won't fix"?

You should update your documentation here to reflect that Github doesn't have branch trigger functionality. It says that it works but then references this issue as a bug in a side note:

+1

I agree.

This feature is a major selling point for the developers loyal to github to embrace jira. the choice of not resolving this feature is a disappointment, indeed.

Is there any way we could make it work with other webhooks or triggers?

+1

+1

+1

+1

Hey Atlassian,

This looks like a super useful feature that people have been asking for over the course of over 2 years and it looks like you've closed it - presumably because you want people to use Bitbucket instead. 

Can you let us know where to track this issue properly?

+1

+1

+1

+ 1

+1. We would really like to be able to use github with jira, in stead of having to manually update everything.

+1

+1

+1

Agree. Sorry, but for me it seems like they don't want to implement that feature due to a market strategy. The required command to create a branch in Bitbucket is the same for Github, both works based on Git. As any Git service, Github does support branch creation of course. So the unique reason I see they still didn't implement it for Github too is because they probably want to show/sell the image of Bitbucket as more advantageous than Github for JIRA.

So please at least put that into your documentation that integration with GitHub is only "read only". You have nice "Make sure you understand how JIRA Software connects to your DVCS account" but there is nothing about lack of this feature. And IMHO without that feature (create branch) is make less sense to integrate JIRA with GitHub.

Hi Megan,

Sorry to bug you, but does "answering a suggestion" mean "we won't do it"? I could equally imagine one answering a suggestion by saying we will do it, so, sorry, but this practice leaves even moderatley intelligent people wondering.

Also, this issue isn't a suggestion. It is an unequivocal feature request and if Atlassian decides not to do it, the clearest course of action is to classify it as a feature request and resolve it as "won't fix". Then as least we know where we are!

Regards,
David

Thanks for bringing this to my attention Lantiq, I've updated the linked issue.