Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-16260

Jira "Create branch" feature creates branch name which is too long for Bitbucket

      Summary

      When creating branch from a Jira issue, if the Jira Summary issue is too long (more than 100 characters), the shortened branch name that is suggested which is shorten is still too long. E.g, for a Jira issue (type story):

      Jira Issue Summary: "123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789" (149 characters)

      Suggested branch name: RTA-5066-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789-123456789 (98 characters)

      Suggested prefix: "feature/" (8 characters)

      That makes a total length of the suggested branch name of 106, more than the 100 characters allowed for a branch name

      This bug will also then lead to the following bug: https://jira.atlassian.com/browse/BSERV-10433

      Steps to Reproduce

      1. Create a Jira issue with a long summary (E.g: 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789)
      2. From the issue page, click 'Create branch', this should redirect to the create branch page on Bitbucket Server
      3. On the branch create page, click 'Create' without changing anything (using the suggested branch name and prefix)

      Expected Results

      Users are able to create a branch on Bitbucket with the suggested branch name

      Actual Results

      Users won't be able create a branch on Bitbucket with the suggested branch name. Instead, they get the error message "The ref name, once fully qualified, is limited to 100 characters", without any possibility to change the branch name.

          Form Name

            [JSWSERVER-16260] Jira "Create branch" feature creates branch name which is too long for Bitbucket

            Kristy added a comment -

            This is a bug in Bitbucket, so it is being tracked at https://jira.atlassian.com/browse/BSERV-11199

            Kristy added a comment - This is a bug in Bitbucket, so it is being tracked at https://jira.atlassian.com/browse/BSERV-11199

            This same bug is also affecting my infrastructure.
            JIRA version 7.5.0 was installed and operating normally with Bitbucket version 5.1.3.

            I upgraded our bitbucket server in February to version 5.8.0 and this issue then began affecting the JIRA branch names.
            I am certainly not an Atlassian developer, but as the JIRA software remained the same, and it was the Bitbucket software which was modified, this may be a bug in the Bitbucket software, not JIRA as specified here.

            admin admin added a comment - This same bug is also affecting my infrastructure. JIRA version 7.5.0 was installed and operating normally with Bitbucket version 5.1.3. I upgraded our bitbucket server in February to version 5.8.0 and this issue then began affecting the JIRA branch names. I am certainly not an Atlassian developer, but as the JIRA software remained the same, and it was the Bitbucket software which was modified, this may be a bug in the Bitbucket software, not JIRA as specified here.

              Unassigned Unassigned
              vchoo Vivian C
              Affected customers:
              16 This affects my team
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: