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.
Bitbucket Data CenterProject Type: software

Bitbucket Data Center

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

Branch Permissions

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.

      One area that I am continually wanting is some fine grained access into branch management. For instance our workflow consists of a developer creating a branch from master and pushing the topic, bug or feature branch upstream. When we go to release to each different environment we have specialty branches (develop, qa and master) which only a few people should have write access to but anyone can read.

      I would like to see some finer grained permissions on who can utilize these different branches to prevent unauthorized writes. What we currently do is manage this in github and we have them issue pull requests then merge the topic branches upstream. Following that we merge them into the specialty branches since they do not have permissions to the upstream repository.

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

            Branch Permissions

            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.

                One area that I am continually wanting is some fine grained access into branch management. For instance our workflow consists of a developer creating a branch from master and pushing the topic, bug or feature branch upstream. When we go to release to each different environment we have specialty branches (develop, qa and master) which only a few people should have write access to but anyone can read.

                I would like to see some finer grained permissions on who can utilize these different branches to prevent unauthorized writes. What we currently do is manage this in github and we have them issue pull requests then merge the topic branches upstream. Following that we merge them into the specialty branches since they do not have permissions to the upstream repository.

                        Unassigned Unassigned
                        mwillbankscb Mike Willbanks
                        Votes:
                        75 Vote for this issue
                        Watchers:
                        74 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              Unassigned Unassigned
                              mwillbankscb Mike Willbanks
                              Votes:
                              75 Vote for this issue
                              Watchers:
                              74 Start watching this issue

                                Created:
                                Updated:
                                Resolved: