-
Bug
-
Resolution: Timed out
-
Low
-
6
-
Severity 3 - Minor
-
156
-
Issue Summary
Assume a user that is NOT watching a repository in Bitbucket, or they are watching it, but they are NOT subscribed to notifications for Pipelines.
If this user pushes a commit or opens a PR that triggers a Pipelines build and this build fails, the user will STILL receive an email notification for it.
This can be confusing for users, since they have unsubscribed for Pipelines notifications in the repo and still receive those emails, and there is no way to turn them off.
Steps to Reproduce
- Stop watching a repository you have access to from the repo's Source page >> ... > Manage notifications
- Alternatively, do not stop watching the repo, but only unsubscribe from Pipelines notifications for this repo
- Configure a bitbucket-pipelines.yml file so you can run Pipelines builds on the repo. Include an invalid command in your script, so that the build fails.
- Push a commit to the repo that will trigger above pipeline.
Expected Results
The build fails and the user does NOT receive an email notification about it, since they have unsubscribed from Pipelines notifications.
Actual Results
The build fails, and the user STILL receives an email notification about it, even though they have unsubscribed from Pipelines notifications.
Workaround
Currently there is no known workaround for this behavior.
- is duplicated by
-
BCLOUD-21632 Pipelines notifications still trigger when disabled/repository is not watched
-
- Closed
-