Uploaded image for project: 'Bitbucket Server'
  1. Bitbucket Server
  2. BSERV-11329

Allow individual users to toggle PR email notifications by event



    • Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 24
    • 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.


      Atlassian status as of Jan 2022

      Hi everyone,

      Thanks to everyone for voting and commenting on this suggestion. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with Bitbucket Data Center.

      We spend a significant amount of time determining our product investments in Bitbucket Data Center. Unfortunately, we are not planning to address this suggestion in the next 12 months. In the last year, we have resolved many of the highly voted suggestions like Reviewer groups, Pull request templates, capability to enable/disable source branch deletion on merging pull requests and our upcoming roadmap includes a number of other top voted suggestions, including repository archiving. Please check out our public roadmap for more details on the coming soon and future items.

      I understand that this may be disappointing, but it’s important for us to be open, honest, and transparent with our customers. Product feedback is collected from many different sources and is evaluated when planning the product roadmap. You can learn more about our process here.


      Anton Genkin
      Product Manager - Bitbucket Data Center & Server

      Original description 

      Currently, Bitbucket sends a crushing amount of emails regarding pull requests, and it's hard to find the useful ones through all the noise. It seems like there are a handful of events that trigger emails, and it would be good if the user could choose to be notified about only the ones they care about:

      • Someone adds me to a pull request
      • Someone approves/denies/etc's a pull request 
      • Someone comments on a pull request
      • Someone merges a pull request
      • Someone adds commits to a pull request.

      I could also see the use case to scope these settings by: 

      • Pull requests I'm reviewing\watching
      • Pull requests I created

      Since someone may care more about approvals and such on their OWN PRs, versus other peoples'. 


        Issue Links



              Unassigned Unassigned
              c78b02791e29 Logan Black
              238 Vote for this issue
              67 Start watching this issue