Uploaded image for project: 'Bitbucket Server'
  1. Bitbucket Server
  2. BSERV-10209

Configure default watchers/subscribers per repo/project

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Pull Requests
    • Labels:
      None
    • UIS:
      9
    • Feedback Policy:
      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.

      Description

      With Bitbucket you can configure the default reviewers that get added to pull requests on a repo and project basis. And after the pull request is created, other individuals can be added as “watchers” to the pull request (https://confluence.atlassian.com/display/STASH0311/Using+pull+requests+in+Stash#UsingpullrequestsinStash-Watchingandnotifications)

      However, there is no way to configure a default set of watchers for the entire repo — who are not required to accept/decline every pull request, but receive notifications about every pull request.

      Phabricator has a notion when creating a code review for two separate lists for the reviewers vs subscribers (the latter akin to stash’s “watchers”).

      With stash, it woudl be extremely useful to specify a default set of watchers could be specified along the default set of reviewers for a project.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              corey26 Corey Steele
              Votes:
              12 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:

                  Backbone Issue Sync

                  • Backbone Issue Sync is enabled for your project, but there is no synchronization info for this issue.