-
Suggestion
-
Resolution: Done
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.
- is duplicated by
-
- Closed
-
- Closed
-
- Closed
- is related to
-
- Closed
-
- Gathering Interest
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BSERV-4203] Add the ability to watch projects, repositories and branches
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?
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.
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.
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?
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.