We couldn't load the project sidebar. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-7414

Ability to default to only use ticket number in the branch name, and not the summary - due to the fact that summaries change

XMLWordPrintable

    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      We are not getting any value from having the long and unnecessary (for us) text of the ticket summary in the branch name. On the contrary, we end up in confusing situations where ticket had one text in the summary, and then the summary was changed to something else. Now we have several cases where different repositories have differently named branches for the same ticket.

      Can we have a system-level setting where there's a toggle between "use ticket only" vs "use ticket and summary" for the branch names?

          Form Name

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Bitbucket Data Center'
            1. Bitbucket Data Center
            2. BSERV-7414

            Ability to default to only use ticket number in the branch name, and not the summary - due to the fact that summaries change

            XMLWordPrintable

              • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

                We are not getting any value from having the long and unnecessary (for us) text of the ticket summary in the branch name. On the contrary, we end up in confusing situations where ticket had one text in the summary, and then the summary was changed to something else. Now we have several cases where different repositories have differently named branches for the same ticket.

                Can we have a system-level setting where there's a toggle between "use ticket only" vs "use ticket and summary" for the branch names?

                        Unassigned Unassigned
                        a7d8cf71caed Pavel Chernikov
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              Unassigned Unassigned
                              a7d8cf71caed Pavel Chernikov
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              2 Start watching this issue

                                Created:
                                Updated:
                                Resolved: