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

Allow individual users to toggle PR email notifications by event



    • Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 20
    • 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 November 2023

      Hi everyone,

      Thank you for your feedback. We appreciate your input and understand the importance of addressing our users' suggestions. Unfortunately, we don't have plans to address this specific suggestion in the next 12 months.

      However, I want to assure you that your feedback is valuable to us. Over the last 12 months we have successfully implemented many highly voted suggestions including code-owners, resolvable comments and auto-merge and our upcoming roadmap includes a number of other top voted suggestions including dark theme, draft pull requests and multi-line comments. For the most up-to-date information on what features are coming soon please visit our roadmap.

      Once again, thank you for sharing your thoughts with us. Your feedback plays a crucial role in shaping the future of our product. We do continually review these priorities and will continue to do so over the coming year to determine when and how we might be able to address this idea. You can learn more about our prioritization process here.


      Sarah Bolt

      Product Manager - Bitbucket Data Center

      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
              244 Vote for this issue
              68 Start watching this issue