We couldn't load all Actvitity tabs. 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-10517

To provide the ability to prevent developers from pull request creation to a particular branch

    • 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.

      I have a project repository on a bitbucket server behind a proxy. I am the administrator for the repository in concern. The ask was to freeze a particular release branch (say, release/1.0) and create a new release branch (say, release/2.0) branching out of release/1.0.

      Is there a way I can prevent the developers from creating a pull request for merging their feature changes to release/1.0? Instead, they should be creating pull requests to merge their changes only to release/2.0.

      Like in the pull request creation page, the target branch dropdown should not show the value - release/1.0. But it should show release/2.0.

            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-10517

            To provide the ability to prevent developers from pull request creation to a particular branch

              • 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.

                I have a project repository on a bitbucket server behind a proxy. I am the administrator for the repository in concern. The ask was to freeze a particular release branch (say, release/1.0) and create a new release branch (say, release/2.0) branching out of release/1.0.

                Is there a way I can prevent the developers from creating a pull request for merging their feature changes to release/1.0? Instead, they should be creating pull requests to merge their changes only to release/2.0.

                Like in the pull request creation page, the target branch dropdown should not show the value - release/1.0. But it should show release/2.0.

                        Unassigned Unassigned
                        1f1bb9d21d86 Satyajit Patnaik
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        2 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              Unassigned Unassigned
                              1f1bb9d21d86 Satyajit Patnaik
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              2 Start watching this issue

                                Created:
                                Updated:
                                Resolved: