Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-10344

As a Administrator I can be sure that the `close branch after a PR is merged` option is checked by default when a new PR is created

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Tracked Elsewhere
    • None
    • None
    • None
    • 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.

          Form Name

            [BSERV-10344] As a Administrator I can be sure that the `close branch after a PR is merged` option is checked by default when a new PR is created

            Bryan Turner (Inactive) added a comment -

            chocolatey030,

            Based on the screenshot on the linked Stack Exchange question, you're referring to Bitbucket Cloud (bitbucket.org), not Bitbucket Server (which doesn't have a "Close branch" toggle on its pull request creation screen). You'll want to raise your issue in their tracker, not here. This tracker is only for Bitbucket Server, and is not monitored by the development team that maintains Bitbucket Cloud.

            Best regards,
            Bryan Turner
            Atlassian Bitbucket

            Bryan Turner (Inactive) added a comment - chocolatey030 , Based on the screenshot on the linked Stack Exchange question, you're referring to Bitbucket Cloud (bitbucket.org), not Bitbucket Server (which doesn't have a "Close branch" toggle on its pull request creation screen). You'll want to raise your issue in their tracker , not here. This tracker is only for Bitbucket Server, and is not monitored by the development team that maintains Bitbucket Cloud. Best regards, Bryan Turner Atlassian Bitbucket

              Unassigned Unassigned
              5accb799bf3f utrecht
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: