This has been open since 2012???

Oops, sorry about that fabian.ritzmann. Should be fixed now.

The survey seems to be misconfigured. When I select "Disagree" for both rows in "How much do you agree with the following statements?", I get: "Please don't select more than one response per column".

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!

Adam Foxson, Every point spot on!

Atlassian, please listen and implement.

We need this feature

How do I like the above comment? 

Pretty dumb that this feature is in cloud version but not server version. It is not right for me to pay additional money for 3rd party implementation that should be native. Come on, this feature should be simple to implement. Just get it done. Thanks

This plugin https://marketplace.atlassian.com/plugins/be.foreach.stash.notifier is not working anymore for versions 4.7 + .

Is this functionality ever going to be implemented natively?

I would like to know if this is planned to be added to the server version of Bitbucket. It's a high need in our organization.

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)

If Stash can sort of let us setup a scheduled commit/push summary notification that would be great.

For example, setup a daily mail sent to specified group of people with a list of commits/pushes happend during the day.

It can gives the development team a general map of the activities without annoying people too much.

Thanks for the link to the alternative 3rd party plugin.

Thanks for the comment Mike. This is on our PM's radar and we're aware of the interest.

Hi - I voted for this, but we've since started using Atlassian's HipChat hosted service + the Stash HipChat notification service. There's no cost to this setup (HipChat is currently free). Our users actually find using the HipChat rooms better for these sort of Stash notifications, rather than getting dozens of e-mails to sift though.We've also got Jira and Confluence (using the Go2Group HipChat plugins) and Jenkins sending room notifications. It works well for our teams right now.

Aware of the workarounds Daniel, but I struggle with paying for a third-party plugin for something that should frankly be a piece of functionality in Stash itself. What is in FishEye is fantastic. That's what I'm looking for.

You guys have a good product here, but I'm frustrated by the lack of attention paid to issues like this and others that have a very high number of votes from your users yet continue to be overlooked. In the case of this one you have >130 votes and >100 comments. Clearly there's a demand for it. So I'd ask again that you guys consider this for an upcoming release in the near future.

Mike

Eric,

We originally used the Push Email Notifier plugin also (Mark, thanks very much for that, it was a big help for us).

We eventually moved to our own roll-your-own solution to provide email notifications when someone makes a commit. Git actually has its own built-in email notification capability. Atlassian's implementation of git within the Stash framework made it only a little more complicated to utilise this feature. Most stock installs of git come with the email notification script, if yours doesn't, just Google it, you'll find many examples. It's actually pretty useable as is.

Put the script (you can add your own modifications to this script for added functionality if you want) in this folder:
<StashHome>/data/repositories/<reponum>/hooks/post-receive.d/
( replace <StashHome> with the path to your Stash Home, and replace <reponum> with its corresponding numerical value. To easily find <reponum>, install the "Repository System Info" plugin, and you will see a Sys Info tab when you browse a repo )

Do that for each repo where you want email notifications when a commit is done. (if you have separate dev teams, you can customise the script for each repo to email only certain people and/or groups)

It ain't pretty, but we get email notifications when a commit is made.

Jon,

It's exactly the FE implementation that I was looking for when I initially created this. I think the FE team did a great job implementing that.

Sadly, I've lost hope that this will get done. Despite this being one of the top vote getters for > a year Atlassian has made no attempt to provide updates or commit to focusing on it. As Stash scales to larger and matrixed organizations this becomes more and more helpful to dev teams. I know Atlassian cares about enterprise scalability around Stash as one of their product managers has reached out to a number of people to set up meetings and I will be bringing this up when I meet with him in a couple of weeks.

Mike

It would be great if Stash supported this. It could use the same approach as what is available in FishEye.

We are using Push Email Notifier Plugin which is free.
See https://marketplace.atlassian.com/plugins/be.foreach.stash.notifier.

@DonMcCasland - Can you please provide additional explanations how you accomplished this with post-receive hooks?

For nearly a year and a half the lack of this feature kept us from purchasing this product, until there were enough other features and our need to host our own repos became so huge we decided to work around it. It turns out to be fairly easy to install the same kind of post-receive emailer hook into your repositories as you would in any other kind of git repo situation.

Yes, it is lame.. as in, a weeping crying shame, lame, for stash not to have a notification scheme as rich and fully thought out as jira, but it is possible to work around.

our experience from having used Notifyr is not very positive either.

I have to say I'm a little disappointed that we are required to use a 3rd party paid plugin to rectify what seems to be a fairly fundamental service that is missing in the application. Moreover, I'm even more disappointed that this issue was raised over 2 years ago and there is seemingly no progress having been made, other than push us to using a paid plugin, thereby increasing our licensing costs for the application.

Hi Mike,

I believe we are much more open than most companies in regards to discussing features and improvements for our products. Providing specific dates or even timeframes is not only problematic from a legal perspective but will inevitably lead to disappointment when dates slip or priorities change.

This feature is a high priority for us and it merely has been pushed back.

Cheers,
Jens

Jens,

Thanks for the response. I understand that you can't commit to specific dates. Although it's frustrating as a customer I can live with it. But it would be helpful to know where it is in the product backlog as I'm assuming you have an issue in your internal Jira instance that mirrors this one. While that wouldn't give us a date it does provide us all with an understanding of how important Atlassian considers this feature vs. others in the backlog.

Is that something you could provide?

Thanks,
Mike

As always, we can not commit to specific dates. However, we can tell you that it won't land in 2013, but it is on our roadmap.

What Mike asked. Is this coming in? If so it will sway our decision making pretty hard.

Jens,

Is this still planned for the November/December timeframe?

Thanks,
Mike

Now that 2.8 is out and I see the road map starting to get filled in for 2.9... are the plans still to have this done for the November/December timeframe?

Thanks,
Mike

Thanks for the update. Really looking forward to seeing this in Stash. It will be a huge help for us.

Mike

We have plans to start work on our next iteration of notifications In November/December. However, at this stage we can not commit to a specific release date.

Any chance of this getting into 2.8?

Do you know how many DEV's have scoffed at our choice of Stash because of the lack of this feature?

I can't defend you guys much longer.

Yes, this is a major issue for us too. Want the feature that is available on bitbucket where I can watch different things. Please, please, please get it in ASAP.

We have almost 80 code repos now, and not every engineer wants to get email for all changes in all repos, but they definitely want to get notifications on repos they subscribe to.

I guess I'll chime in and say that this is a key feature for us too. This should be core functionality, like watches in JIRA. It will become much more important as our production code teams begin to use our Stash instance.

This is the entire reason we have not bought and rolled out this product yet for our 500 users. Last time I evaluated the Notify plugin it was also toyish.

I don't see a business value field for this ticket, but it should be 100.

This feature is really the crux that makes stash look like a toyish "me-too" product compared to github enterprise.

Yep. Not there.

Has anyone taken a look at the latest releases? There have been 3 releases since this bug was logged, and I thought I saw a mention that this functionality was put in.

Our roll out of Stash is imminent now so this is going to be becoming more and more critical shortly for us as well. The Notifyr plugin is close to what we need, but it's not quite there. More importantly, though, I'm struggling to understand why this isn't something that would be considered core functionality of Stash that would warrant the time and effort to implement a Confluence like "Watch" for notifications. Given that this issue is one of the top 5 vote getters it seems that others would agree with that.

Mike

I'm also eager to get my hands on this for my company. Keeping up to date on what is happening is all a part of team collaboration and communication. So far we've been evaluating Notifyr, but I can imagine like others have said, if this showed the granularity of changes that JIRA and Confluence do for instance; all built-in, it would be amazing to say the least. Thanks.

Any update on this feature ... the plugins out there are pretty limited. Looking for any indication that this is still being actively worked on.

One more thing I'd like to add:

The developers are pretty upset with the limited functionality of the Notifyr plugin. They want to be able to see the changes in the body of the email, like we can do on SVN. (I did mention template-like emails in my previous post)
There should be a place where we can configure the notifications to be as granular as we want, so that one user can turn them off entirely while another user can subscribe to every type of notification(can we get notified when people clone?) I wanted to add these two details so that the feature would be as rich as possible and not leave people wanting more.

Well, I'm a little stymied by the decisions here. I know they aren't even close to the same code base, but the granularity of notifications for Jira are perfect, and what I had hoped for with Stash.

That being said, Stash is moving along very quickly, and they might have this ready next release. Everyone vote for built-in push notification hook!

@Don McCasland - Good choice, we just rolled out Stash here and I underestimated that notifications as a feature would be such a deal-breaker. I went from being a good guy to being a bad guy once everyone realized they aren't getting notifications! This should be escalated to highest priority. Truth is, I don't think people should even be PAYING for an application without such a simple functionality included.

I'm afraid that the inability to email either a list of people or individuals is a non-starter for rolling this out at our company. Our engineering process is pretty set. We use a mail hook to email lists to watch all changes. If we can't do the same thing with Stash then we have to use something else for repository management.