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

Add the ability to watch projects, repositories and branches

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

      Update: Shipped in Bitbucket Server and Data Center 5.10 

      Original request description

      One problem our developers are starting to have now that we've migrated to Stash is keeping on top of changes in repositories that we make use of but don't directly develop. Our deliverable projects are large and made up of multiple smaller component projects each with multiple repositories (it all adds up to hundreds of repositories in a final deliverable project).

      It would be very useful to our developers if they could receive emails on changes being pushed to the server for certain parts of the code that are of especial interest to them. You already have the concept of watching a pull request, it would be nice if this could be extended to allow a user to watch:

      1. A branch - See any pushes to that branch
      2. A repository - See any pushes to that repository on any branch
      3. A project - See any pushes to any branch of any repository in that project.

      A REST API to add and remove yourself as a watcher would also be usefull so we can script setting up watch lists accross entire projects if need be.

      While there are some plugins that allow this a lot of the time they require admin permissions to the module to allow you edit the plugins email settings to add and remove users. Watching should only require read permissions to a repository as it doesn't require making any changes.

            [BSERV-4203] Add the ability to watch projects, repositories and branches

            Imran Khan added a comment -

            Hi everyone,

            Thanks for your feedback and advocacy on this issue. The ability to watch repositories is part of Bitbucket Server and Data Center 5.10. Please check it. We don't have any short-term plans to implement the ability to watch projects (part of the original request). If you're keen on that I would recommend creating a separate issue for better tracking and getting specific feedback. I'll be closing this issue.

            Cheers.

            Imran Khan added a comment - Hi everyone, Thanks for your feedback and advocacy on this issue. The ability to watch repositories is part of Bitbucket Server and Data Center 5.10 . Please check it. We don't have any short-term plans to implement the ability to watch projects (part of the original request). If you're keen on that I would recommend creating a separate issue for better tracking and getting specific feedback. I'll be closing this issue. Cheers.

            Ian Neal added a comment -

            This would be a great feature. 

            Another case we have is being notified of changes on a project & branch at the directory (ie anything change to anything beneath the directory) or even the file level.

            So out DBAs know some SQL was changed or a jar was added so the license needs to be verified etc...

            Hopefully this feature will make in as it would be very useful to improve notifications in all of these areas.

             

             

            Ian Neal added a comment - This would be a great feature.  Another case we have is being notified of changes on a project & branch at the directory (ie anything change to anything beneath the directory) or even the file level. So out DBAs know some SQL was changed or a jar was added so the license needs to be verified etc... Hopefully this feature will make in as it would be very useful to improve notifications in all of these areas.    

            Hi, I completed the survey. Do we have any Timeline when we can see this feature on server Bitbucket?

            devops@mobileiron.com added a comment - Hi, I completed the survey. Do we have any Timeline when we can see this feature on server Bitbucket?

            Jess Ruyter (Inactive) added a comment - - edited

            Hi all,

            Thanks for your continued interest and feedback on this suggestion. In considering everyone's feedback, and what we've learnt from similar functionality in other places, we're keen to understand the diversity of opinion on this suggestion in a little more detail to ensure we build something useful. To help us understand requirements around repository notifications, it would be great if you could all fill out this brief survey-

            https://goo.gl/forms/58LIPuoGeVlszdao1

            Thanks in advance!

            Jess Ruyter (Inactive) added a comment - - edited Hi all, Thanks for your continued interest and feedback on this suggestion. In considering everyone's feedback, and what we've learnt from similar functionality in other places, we're keen to understand the diversity of opinion on this suggestion in a little more detail to ensure we build something useful. To help us understand requirements around repository notifications, it would be great if you could all fill out this brief survey- https://goo.gl/forms/58LIPuoGeVlszdao1 Thanks in advance!

            We are working in an onshore / partnered offshore development model with shared repo (on branches, of course). Our offshore must know when onshore merges / commits to a Release branch. Notifications without adding approvers manually is critical, especially for hambone commits directly to the Release branch without branching and a merge. Please, please: Please implement this feature in Server.

            Dan Blechinger added a comment - We are working in an onshore / partnered offshore development model with shared repo (on branches, of course). Our offshore must know when onshore merges / commits to a Release branch. Notifications without adding approvers manually is critical, especially for hambone commits directly to the Release branch without branching and a merge. Please, please: Please implement this feature in Server.

            Jon Kokko added a comment -

            You'd think that this would be core functionality instead of a $2800 plugin.

            Jon Kokko added a comment - You'd think that this would be core functionality instead of a $2800 plugin.

            Ouch! Thx. I didn't realize that they just rebranded Stash. That's too bad. The word of mouth that I've read on Twitter is not too kind to Stash. I'm wondering if they are separate codebases. That would be a serious problem.

            Eric Pederson added a comment - Ouch! Thx. I didn't realize that they just rebranded Stash. That's too bad. The word of mouth that I've read on Twitter is not too kind to Stash. I'm wondering if they are separate codebases. That would be a serious problem.

            nickbroon added a comment -

            I'd guess a lot more!
            There are tickets with well of 400 votes and that have been open for 5 years that aren't implemented: https://jira.atlassian.com/projects/BSERV/issues/?filter=allopenissues&orderby=votes

            nickbroon added a comment - I'd guess a lot more! There are tickets with well of 400 votes and that have been open for 5 years that aren't implemented: https://jira.atlassian.com/projects/BSERV/issues/?filter=allopenissues&orderby=votes

            This one has 75 votes. How many votes does something need to put it on the roadmap?

            Eric Pederson added a comment - This one has 75 votes. How many votes does something need to put it on the roadmap?

            Hi lee1001, our aim is to ensure the products offer the same core code collaboration capabilities around branches and pull requests, and we're working on closing gaps over time. That said, there isn't a guarantee that we'll reach full parity across every feature. Over time we learn from the popularity of features in each product about which are valuable to have in the other. This suggestion is high on the list of candidates to be brought into line.

            Roger Barnes (Inactive) added a comment - Hi lee1001 , our aim is to ensure the products offer the same core code collaboration capabilities around branches and pull requests, and we're working on closing gaps over time. That said, there isn't a guarantee that we'll reach full parity across every feature. Over time we learn from the popularity of features in each product about which are valuable to have in the other. This suggestion is high on the list of candidates to be brought into line.

            Thanks Roger – Do you know if it is on the radar as a stated goal to actually bring parity between the Bitbucket Cloud and Bitbucket Server?

            Ian Lee [LLNL] added a comment - Thanks Roger – Do you know if it is on the radar as a stated goal to actually bring parity between the Bitbucket Cloud and Bitbucket Server?

            Hi Ian,

            We agree that these would be useful improvements. We are working on some related dependencies towards this capability but unfortunately don’t have it on our near term roadmap.

            Roger Barnes (Inactive) added a comment - Hi Ian, We agree that these would be useful improvements. We are working on some related dependencies towards this capability but unfortunately don’t have it on our near term roadmap.

            Has there been any update on this? The functionality is available in Bitbucket Cloud (https://confluence.atlassian.com/bitbucket/manage-inbox-and-email-notifications-325321743.html#ManageInboxandemailnotifications-Configurerepository-widenotifications), and is a pretty severe limitation for some of our development teams.

            It would be great to get this added natively, instead of via plugins (e.g. Notifyr https://marketplace.atlassian.com/plugins/nl.stefankohler.stash.stash-notification-plugin/server/overview)

            Ian Lee [LLNL] added a comment - Has there been any update on this? The functionality is available in Bitbucket Cloud ( https://confluence.atlassian.com/bitbucket/manage-inbox-and-email-notifications-325321743.html#ManageInboxandemailnotifications-Configurerepository-widenotifications ), and is a pretty severe limitation for some of our development teams. It would be great to get this added natively, instead of via plugins (e.g. Notifyr https://marketplace.atlassian.com/plugins/nl.stefankohler.stash.stash-notification-plugin/server/overview )

            I second Kimmo Toro's suggestion about adding the ability to watch pull requests. I'm less concerned about commits and branches as I am about seeing pull request activity in projects and repositories I have a vested interest in.

            Right now, we have a (not great) workaround to this which is to require all developers to list EVERY team member on EVERY Pull Request and in the Overview section list out who is actually required to approve the PR.

            Letting our team members subscribe to pull requests in repositories they have an interest in will put the choice in their hands when they'd like to chime in before things get merged.

            Matt Merrill added a comment - I second Kimmo Toro's suggestion about adding the ability to watch pull requests. I'm less concerned about commits and branches as I am about seeing pull request activity in projects and repositories I have a vested interest in. Right now, we have a (not great) workaround to this which is to require all developers to list EVERY team member on EVERY Pull Request and in the Overview section list out who is actually required to approve the PR. Letting our team members subscribe to pull requests in repositories they have an interest in will put the choice in their hands when they'd like to chime in before things get merged.

            I found the same Benjamin, but, it was hard enough getting the initial license for Stash signed off, let alone adding the plugin. Although it does it look good, I also feel this should be core functionality. JIRA and Confluence have flavours of notifications. Stash should similarly follow suit

            Shaun Bokenham added a comment - I found the same Benjamin, but, it was hard enough getting the initial license for Stash signed off, let alone adding the plugin. Although it does it look good, I also feel this should be core functionality. JIRA and Confluence have flavours of notifications. Stash should similarly follow suit

            I thought I'd point out that there is a plugin called Notifyr which offers all of the functionality mentioned above and then same (includes a favourites tab + drop-down) for a decent price for those who are interested.

            While I also understand that this feature should really be implemented into the core of Stash, as juggling with 3rd-party plugin dependencies can become tiresome when required to upgrade your Stash instances and not to mention the potential security concerns which might arise for some companies/customers/clients.

            So with that being said, +1 from me

            Benjamin D. Smith added a comment - I thought I'd point out that there is a plugin called Notifyr which offers all of the functionality mentioned above and then same (includes a favourites tab + drop-down) for a decent price for those who are interested. While I also understand that this feature should really be implemented into the core of Stash, as juggling with 3rd-party plugin dependencies can become tiresome when required to upgrade your Stash instances and not to mention the potential security concerns which might arise for some companies/customers/clients. So with that being said, +1 from me

            This feature would be really useful for several teams of ours as the teams want to keep track of work done. Our teams use heavily the pull request based way of working with mandated code reviews.

            Kimmo Helsing added a comment - This feature would be really useful for several teams of ours as the teams want to keep track of work done. Our teams use heavily the pull request based way of working with mandated code reviews.

            If (and when) this is implemented please also consider being able to watch all new pull requests in a project or a repository. We have several use-cases with common repositories where several people can contribute to using pull requests. It is not always known who will be the ones approving the pull requests so it is not possible to @mention those people or mark them as reviewers in a new pull request.

            The people who are responsible for reviewing and merging the new pull requests would like to be able to subscribe to certain repositories to be able to get e-mail notifications on all new pull requests on those repositories (but only those).

            In addition, it would be great if one could define default reviewers per repository or project. So that when a pull request is created, there would be already some names filled in as reviewers.

            Kimmo Helsing added a comment - If (and when) this is implemented please also consider being able to watch all new pull requests in a project or a repository. We have several use-cases with common repositories where several people can contribute to using pull requests. It is not always known who will be the ones approving the pull requests so it is not possible to @mention those people or mark them as reviewers in a new pull request. The people who are responsible for reviewing and merging the new pull requests would like to be able to subscribe to certain repositories to be able to get e-mail notifications on all new pull requests on those repositories (but only those). In addition, it would be great if one could define default reviewers per repository or project. So that when a pull request is created, there would be already some names filled in as reviewers.

              Unassigned Unassigned
              andrew.milne1 andrew.milne1
              Votes:
              189 Vote for this issue
              Watchers:
              130 Start watching this issue

                Created:
                Updated:
                Resolved: