Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-23159

Additional branch type to better differentiate between the unmerged branches

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Issue Summary

      The calculation of merged vs active branches is done by considering the default branch (not by the creation time), if a new branch is ahead of default then it is considered as an active branch hence a newly created branches which are not merged using PR still shows up on the merged branches list.

      It would be better if there can be an additional type of branches to better differentiate between the branches instead of using only merged and active branches.

      Steps to Reproduce

      1. Create a branch test, merge the branch with master. Test branch will be listed in the merged branches. 
      2. Create another new branch test_new from test branch, since this branches is created from an already merged branch, the master is updated with the updates already and hence the newly created branch test_new also gets listed in merged branches.

      Expected Results

      Since the branch was not merged and sometimes teams have even not started working on it, it should be listed in active branch. 

      Actual Results

      The branch shows up as merged branch.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

      Attachments

        Activity

          People

            Unassigned Unassigned
            76af9768c127 Snigdha Mishra
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: