Branching models for BB Cloud

Issue #12833 open
Janusz Skonieczny
created an issue

Official response

  • Martin Jopson staff

    Thanks for commenting, voting and watching this issue.

    The team has now shipped branching model support for all Bitbucket repositories. To avoid unwanted surprises existing repositories do not have the feature enabled by default so you’ll need to enable it in the repository settings to enjoy the benefits. New repositories will have the feature enabled by default.

    When enabled, the default branch type names are set to Bugfix, Feature, Hotfix, and Release. These can be individually turned off, or edited, to match your naming convention. Choosing the Other option will not prefix the branch with one of the configured branch types.

    When Jira Software and Bitbucket are connected, creating a branch from Jira Software will take advantage of smart mapping which automatically selects the branch type depending on the Jira issue type, bug → Bugfix and story → Feature

    Further details are available in the documentation at branching model.

    We trust this will better support your teams process. This is the first step to help your teams work with branches more easily, so we'd love to hear your feedback.

    Kind regards,
    Martin
    Bitbucket Product Manager

Comments (178)

  1. Anonymous

    Oh, so much inconsistency between server and cloud ... ! I can understand that cloud has more advanced features than server editon, but not less! This is really something that need to be added.

  2. Nikita Magonov

    It is very strange that BB Server and BB Cloud have different functionality.

    What is the development status of this issue? Looks like there are no any actions from Atlassian team since the issue was opened.

  3. Alastair Wilkes staff

    Hi y'all,

    Thanks for your interest and enthusiasm around this feature. We definitely agree that it's very useful and is something we'd like to bring to Cloud at some point, but at this time we do not have an ETA. We'll update this issue when we have more information.

    Thanks, Alastair

  4. Perry Moutzouros

    So of course I get to a new team and swear this feature is awesome. And then realize that they have cloud instead of server (where I had grown used to this awesomeness) and now I make the sad face. Come on Atlassian. Ive spent my entire career watching you guys miss the target on important features on the server. And now that everyone is moving to the cloud? Another round of "we'll get to it?" Sheesh.

  5. Dino

    +1, the main reason why we wanted to choose to use BB Cloud and not github or regular. Can't fully relocate to BB cloud from regular git cuz' of this feature

  6. Alastair Wilkes staff

    Hi y'all,

    Thanks for your interest in this feature! This is still in the backlog, but it's lower priority than other projects at this time. We'll update this issue when it's going to be worked on.

    Thanks,

    Alastair

  7. Jay Chau

    How do I leverage the pipeline and JIRA without this?

    What I want to do is when ticket closed, code marge to staging branch and deploy to staging server.

  8. Anonymous

    Wow this is crazy, it was one of the factors for wanting to migrate my team away from Github and now I find out that this feature doesn't even exist for cloud.

  9. Aaron Brockhurst

    I'm stunned that BB Cloud doesn't support this, especially as there's a section devoted to it in the help docs and it's clearly an essential part of most teams development lifecycle.

  10. Simon Stevens

    quoting Aaron above, I can't believe that BB Cloud doesn't have this essential component when it's heavily supported in BB Server and used by most dev teams.

    We're just completing our move from BB Server, and it's pretty devastating to discover this missing functionality. Now I'm worried about what else we are going to find isn't supported.

  11. Anonymous

    I've migrated away from Atlassian Cloud products. There are a lot of problems like this throughout their cloud products. Stick to server until cloud is ready for actual production use, cloud seems more like a beta to me.

  12. Rylan Cates

    +1 - Pretty interesting decision to leave out something so integral to git workflows... Definitely cramping our team's workflow. I would have thought that this would be prioritized over 'style changes'.

    Also, +1 for reasons we're considering Gitlab and JetBrains tooling.

  13. Jo Peel

    +1 Hey Folks! Surely this feature is needed to support seamless Jira & Bitbucket git workflow model in my, and any other, team. I've just come across this issue after ages searching for the feature. I guess there are work-arounds, but they are, well, work-arounds. Seems odd that it didn't make it from the server to the cloud. Looking forward to seeing an ETA.

  14. David Wahlandt

    +1

    1 1/2 year and no progress on this missing feature? Can't you just host Bitbucket Server yourself and call it Bitbucket Cloud :'D

    but seriously, that one should get bumped up the backlog quick

  15. Chris Seegers

    +1 Moved from Bitbucket Server (former name Stash) to Bitbucket Cloud to reduce cost and have a worry-free availability and up-to-date solution. (Our Atlassian software didn't get updated). However, not having this feature in the Cloud version, whilst having it in an old Stash version, lead to a moment thinking of 'did we make the right choice??'

  16. Erik Niese-Petersen

    +1

    We enabled GitFlow in SourceTree on some repositories then was very disappointed in finding out that it is still not supported in BitBucket Cloud when we try and create branches from JIRA tickets.

  17. Martin Jopson staff

    Thanks for your feedback on this ticket. We review our highest voted issues regularly, and have just completed this process again.

    Unfortunately, we don't have any plans to address this feature right now. At the moment, we're busy improving Bitbucket in the following areas:

    • Pull requests
    • Code search
    • Pipelines & Deployments
    • Design and User Experience

    Please continue to follow this ticket for updates, and add comments describing any use-cases that are important to your team and not already covered above.

    Kind regards,

    Martin

  18. Bert Oost

    Robert, You can, if you don't use branch permissions that disallow you to push directly to develop/master. Therefor; if you also use JIRA, it can be useful to create the branch from a story or task.

  19. Robert van Mölken

    Bert, that is how we create branches, but in the Cloud version I have not yet found a way to show a dropdown list so I for example can make a feature/name, version/name or release/name branch from Jira.

    I can only select from where to branch from. Currently I need to add feature/ myself infront of the branch name created by Jira.

    I the server version this is possible with branching models.

  20. Allan Hsu

    It's really deceptive advertising that the feature comparison between the Cloud, Server, and Data Center products on the Atlassian product site makes it look like Cloud has a superset of the Server features, but it actuality, Cloud is a completely different product that's missing this feature, along with many other desired features from Stash/Server, like automatic merges and a tree view for diffs. These distinctions should be made clear; otherwise people may make the mistake of evaluating Server and then choosing to go with Cloud for pricing or ease of maintenance reasons, expecting to get (at bare minimum) the same feature set.

  21. Rylan Cates

    The tree view for diffs being missing is incomprehensible in my opinion. We're left with a giant vertical scroll between us and a decent pull request review... That said, I feel your comment is spot on. We are now hosed and having to find time to spend converting over to a different product rather than working on OUR product. It seems they value extracting and productizing crucial features more than they care about usability.

  22. Derek Rosien

    When is this going to be implemented ????? This is something that my team, and I am sure a number of others, would cause to switch to another product/solution.

    Please implement this, the fact that server has this and cloud does not is crazy...

  23. Egor Drozdov

    +1 Still not implemented? I've just won a huge discussion about switching to bitbucket, presenting the Atlassian's video from 2014 showing this feature. What do i say to my developers now, when we switched? :) Looks very strange...

  24. Alex Söhn

    +50 from me and the whole dev team. We definitely need this! Cloud and Server are too absolutely different and disjunct projects, don't try to move from server to cloud, rather find a different product...

  25. Quentin Hello

    +99 It’s completely lunatic in my dev team opinion that this is not part of BB cloud yet. This lack of features between cloud and server seriously make us regularly question whether or not we should stick with BB over another solution...

  26. Pawitter Rao

    This is really an important feature which should be added to bitbucket cloud. We use both cloud and server version and there is inconsistency across the features and alot of things we can't do with cloud version. +1

  27. Martin Jopson staff

    Thanks for your feedback on this ticket. We review our highest voted issues regularly, and have just completed this process again.

    Unfortunately, we don't have any plans to address this feature right now. At the moment, we're busy improving Bitbucket in the following areas:

    • Pull requests
    • File search
    • Deployments
    • Integrations

    Please continue to follow this ticket for updates, and add comments describing any use-cases that are important to your team and not already covered above.

    Kind regards,

    Martin

  28. Robert Watkins

    @Martin Jopson, this is the 6th highest voted issue. If you add in the votes from the issues that duplicates this one, it falls in the number 3 slot. It's fully part of the "Integrations" section - #8216, which was marked a duplicate of this one, relates to creating branches from JIRA. It's a feature that apparently works in BitBucket Server.

    You may review your highest voted issues regularly, but the top 8 issues are all several years old. Heck, this one is almost five years old if you use #8216 as the start date. On the entire first page, nearly every issue is 4+ years old. This is a strong indication that you don't actually care about the highest voted issues.

    All this issue is asking for is the option to configure the name pattern when creating issues from JIRA (or other linked product). It's not a massive re-architecture - it's a regex and a configuration value in the settings.

  29. Derek Rosien

    Seconding the reply from @Robert Watkins, well said...

    Take a serious look at what your customers are asking, that is how you run a good business... If it the decision were up to me at my workplace, we would not be using this product due to things like this.

    I am hoping to be proved wrong soon, but based on some replies I have little faith.

  30. Robert van Mölken

    Thanks @Robert Watkins for looking into the correct statistics.

    @Martin Jopson , I just can't understand why such a minor change can be constantly postponed, but has a enormous value to a lot of customers.

    This issue can be fixed easily be fixed just as @Robert Watkins proposes with a simple configuration of the value under the project settings. It is voted so high that it can easily be added as a sprint filler.

    It is really a shame that we as well-invested customers are not taking serously.

  31. Chris Diana

    Totally agree. This is unreal. I don't understand this at all. Here are active, paying users taking time out of their own day to give valuable feedback to improve your product. Obviously Atlasssian/Bitbucket doesn't value their customers feedback (or time) as much as they say because if they did this issue that is almost 2 years old (and one of the top suggested features) would have been acknowledged and resolved.

  32. David Wahlandt

    there shouldn't be a difference between both products in the first place. You are hosting one product and the other is hosted by us. That should be the only difference. So your top priority should be to keep both products in sync (or just use the same for both). It's ridiculous to even argue about this.

  33. Brian Kinder

    I didn't even realize this was a missing feature until we had already committed to using bitbucket cloud. Had I known this was missing, we would have gone somewhere else. Even though we're sticking with bitbucket cloud for now, we decided not to invest in Bamboo for our CI needs to make it easier for us to separate in the future.

  34. Robert Watkins

    @David Wahlandt - BitBucket Server is literally a different product to BitBucket Cloud. BitBucket Cloud is the original, acquired by Atlassian several years ago. They then acquired another product (I forget the name), and reskinned & rebranded that as BitBucket Server. It already had this feature, so they kept it - but they haven't put it into Cloud. That's a big reason why there are feature disparities between Cloud & Server.

    The lack of this feature isn't the end of the world. It's easily worked around - it's just annoying as hell.

  35. David Wahlandt

    @Robert Watkins I wasn't aware of the history, but i know that these are two separate products. Either way, and especially because they've changed the naming of Stash to make it more closely related to BitBucket, there should be no difference in features between the two. Otherwise they should have kept the old name to distinguish them. With the current names you just expect that BitBucket Server is exactly the same as BitBucket except that you are going to host it yourself and that is not the case, not only with this feature.

  36. casaliz

    +1 I was amazed to find out this is not implemented. What's the point of using git-flow if your tools don't assist you with it? I still haven't committed to bitbucket yet, since docker gives two choices between github and bb, i might just end up switching to github if it takes 5 years to even consider this as a feature by the devs.

  37. Martin Jopson staff

    Thanks for voting, watching and commenting on this issue.

    [updated] The team in Sydney are currently looking at this enhancement and have now scheduled time with a number of you to better understand needs, expectations and how these teams work.

    Kind regards,
    Martin
    Bitbucket Product Manager

  38. Agata Philipp

    It would be great if this feature would preselect the type of branch based on issue type when creating the branch via Jira integration, e.g.:

    • if jira issue is bug type -> preselect bugfix branch type
    • if jira issue is story type -> preselect feature branch type

    Even better if such mapping was configurable.

    But just having the feature added at all to Bitbucket Cloud will be great already :)

  39. Asiri Dalugoda

    How did anyone came up with the idea of having a cloud version with limited functionalities. I dont see forks either in cloud version and this is 2018/08 I'd love to see the branching model in cloud. Seems no one taking action on this case eventhough its being marked Major since 2016 I have no other option than unsubscribing and move to a competitor who better responds to customer requests.

  40. Jay Chau

    It's really not cool to tell our developer "Every time you create a feature branch please remember to put the prefix 'feature/' in front of it".

  41. Martin Jopson staff

    Thanks for voting, watching and commenting on this issue.

    The team are currently working on this enhancement, further details including its availability will be added here in due course.

    Kind regards,
    Martin
    Bitbucket Product Manager

  42. Martin Jopson staff

    Thanks for commenting, voting and watching this issue.

    The team has now shipped branching model support for all Bitbucket repositories. To avoid unwanted surprises existing repositories do not have the feature enabled by default so you’ll need to enable it in the repository settings to enjoy the benefits. New repositories will have the feature enabled by default.

    When enabled, the default branch type names are set to Bugfix, Feature, Hotfix, and Release. These can be individually turned off, or edited, to match your naming convention. Choosing the Other option will not prefix the branch with one of the configured branch types.

    When Jira Software and Bitbucket are connected, creating a branch from Jira Software will take advantage of smart mapping which automatically selects the branch type depending on the Jira issue type, bug → Bugfix and story → Feature

    Further details are available in the documentation at branching model.

    We trust this will better support your teams process. This is the first step to help your teams work with branches more easily, so we'd love to hear your feedback.

    Kind regards,
    Martin
    Bitbucket Product Manager

  43. Ben Tatham

    Thanks for this.

    Capture.JPG

    Except the enforcement that Prefix for branching types may not overlap means that we can't use it with the standard git flow model, where bugfix and features are both /feature. If we did change to these distinct prefixes, it would also mean defining new Pipelines for them, when we treat them the same for a "feature" pipeline.

    Put another way, we want Story and Bug issue types in Jira to both map to /feature.

    So close...

  44. Chris Seegers

    I am SO happy this has been implemented !!

    In fact, I'm so happy, that my mood has improved significantly. Due to this, my colleagues get free coffees from me, and I now compliment them for everything and nothing. While driving in traffic, I'm not a prick anymore. I wait patiently in line and let other people go in front of me. My wife is now back with me, because I have no anger issues anymore and my dog is not afraid of me anymore. This change has affected my life dramatically, as you can read. My manager thought I won the lottery or something, but no, applying a branching model makes me very happy.

    All that remains for me to say is: THANK YOU!

  45. Allan Hsu

    When Jira Software and Bitbucket are connected, creating a branch from Jira Software will take advantage of smart mapping which automatically selects the branch type depending on the Jira issue type, bug → Bugfix and story → Feature

    @Martin Jopson , I can't figure out how to get the mapping to work. Is a specific version of Jira Software required?

  46. Robert Watkins

    @Allan Hsu You configure the mapping of issue type to branches in Bitbucket (using Bitbucket issue types) on a per-repository basis. You get to it from the Settings panel for the repository.

    https://confluence.atlassian.com/bitbucket/branching-a-repository-223217999.html#BranchingaRepository-model

    It would have been nice if this was able to be configured on a project level - I'm currently going through a few dozen repositories for my main project to configure this.

  47. Log in to comment