When creating a Linked Repository of type GitHub, the Branch dropdown shows a maximum of 30 branches.
      If the GitHub repository has more than 30 branches, the dropdown gives no indication that there are more than the 30 branches shown, nor gives it you a way to select a branch that is not shown.

          Form Name

            [BAM-15686] GitHub repository shows only 30 branches

            hmm i have on demand but im still on 5.8.1

            Bianca Morton added a comment - hmm i have on demand but im still on 5.8.1

            This appears to be fixed in the on demand version since the Bamboo 5.10-OD-4 push - I can see all of my branches!

            Ryan Alexander added a comment - This appears to be fixed in the on demand version since the Bamboo 5.10-OD-4 push - I can see all of my branches!

            Having the same issue, we have lost a lot of time cleaning up branches just so we can get the correct branch to appear in the drop-down...

            Ryan Alexander added a comment - Having the same issue, we have lost a lot of time cleaning up branches just so we can get the correct branch to appear in the drop-down...

            Here is a workaround: right click the select box and going to inspect element. Where it shows all the <option>branch</option> just rename one of the "branch" fields with your desired branch and hit enter. Then without refreshing the page select that option and save.

            An easy solution to get this solved quickly would be to allow us to type in the branch name!

            Bianca Morton added a comment - Here is a workaround: right click the select box and going to inspect element. Where it shows all the <option>branch</option> just rename one of the "branch" fields with your desired branch and hit enter. Then without refreshing the page select that option and save. An easy solution to get this solved quickly would be to allow us to type in the branch name!

            Also plese make this issue a blocker. we cannot set up our builds without this and therefore cannot use bamboo at all

            Bianca Morton added a comment - Also plese make this issue a blocker. we cannot set up our builds without this and therefore cannot use bamboo at all

            please fix this or provide a work around, even if it code. I cannot delete work branches to get the main branch under position 30

            Bianca Morton added a comment - please fix this or provide a work around, even if it code. I cannot delete work branches to get the main branch under position 30

            We would also like to see more than 30 branches. There are a number of companies that have developers work there change on a branch (feature branch) and then merge that back in with the master code line or whatever code line is built.
            Having a limit of 30 makes it painful to have to go and disable branches just to get your branch to show.

            lance_lyons added a comment - We would also like to see more than 30 branches. There are a number of companies that have developers work there change on a branch (feature branch) and then merge that back in with the master code line or whatever code line is built. Having a limit of 30 makes it painful to have to go and disable branches just to get your branch to show.

            Forgot to mention we're running into this on Bamboo 5.8.1 build 5866.

            Deleted Account (Inactive) added a comment - Forgot to mention we're running into this on Bamboo 5.8.1 build 5866.

            This is causing a lot of issues for how we build right now as well. Would be great to see this issue fixed. Thanks.

            Deleted Account (Inactive) added a comment - This is causing a lot of issues for how we build right now as well. Would be great to see this issue fixed. Thanks.

            Issue is critical for our project too - right now we have a lot of branches(for each development sprint) and half of them cannot be used.

            Arthur Gurov added a comment - Issue is critical for our project too - right now we have a lot of branches(for each development sprint) and half of them cannot be used.

            This is critical to our current build. We are using a default branch that is not master and we cannot find it in our repo list.

            Aaron Drake added a comment - This is critical to our current build. We are using a default branch that is not master and we cannot find it in our repo list.

              Unassigned Unassigned
              rverschoor Rene Verschoor (Inactive)
              Affected customers:
              12 This affects my team
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: