To my understanding, this is a violation of the EU's GDPR (General Data Protection Regulation) that has to be addressed.

After reviewing this issue, we determined that it was low priority and unlikely to be worked on in the near future. We appreciate your input, but want to be transparent about our decision to not fix this right now. 

I'm also getting a lot of Bitbucket emails for failed (mostly scheduled) pipelines for many repositories of my organization even though I am not "watching" those repositories, and have turned off all email notifications of that kind I could find. It appears however that I only get these notifications if the pipeline ran on a commit I authored. This seems like a bug on Bitbucket's part. Ideally I'd only like to get those notifications on repositories which I watch and on which I've enabled pipeline notifications. The only workaround with which I could come up so far is to enable some specific mailbox rules to send these straight into the junk folder.

How do I turn off the notifications for a failing pipeline that I want to ignore, without turning off all other notifications for that repository?  I'm not even subscribed to the pipeline notifications but I'm still getting them when a pipeline fails and I have no idea why or how to turn it off; the docs are absolutely terrible and this is the only thing I can find in google but it leads me on a loop.

We use TDD with CI/CD; I just want to turn off build failure notifications that we expect; otherwise I run the risk of team members ignoring them in their email client and that creates even worse issues once they start to matter.

Thanks for documenting this here, Tyler.

This information doesn't appear in the documentation where I would expect: https://support.atlassian.com/bitbucket-cloud/docs/manage-email-notifications-for-watched-objects/

The page about watched object notifications doesn't mention pipelines at all.

I think it's important to mention them explicitly because a common pattern on a small projects is to have a single user committing directly to the master branch with a single pipeline. That user won't receive any notifications about their own commits, and there are no PRs, forks, issues or wikis to notify about.

But there are a lot of pipeline failure notifications. So, so many failure notifications...

Attachment 3690918690-Screen%20Shot%202018-10-10%20at%2010.58.33%20AM.png has been added with description: Originally embedded in Bitbucket issue #16983 in site/master

Attachment 370878609-Screen%20Shot%202018-10-10%20at%2010.57.58%20AM.png has been added with description: Originally embedded in Bitbucket issue #16983 in site/master

Notifications options have been added to the New Source Browser. Open the Manage notifications menu option in the source browser menu to manage your repository subscriptions.