Issue #7304 new

Notification email (BB-8500)

Mehmet Catalbas
created an issue

The new notification system overhaul is nice, thanks a lot! However, I should be able to receive emails to any email address I have verified, not necessarily my primary email address associated with my identity.

In short, I should be able to select a notification email address in the notifications settings.

Comments (8)

  1. Michael Frauenholtz staff

    Hi Mehmet,

    Thanks for the suggestion! We've had a few short discussions about user email addresses, but haven't decided anything concrete yet. I've added this ticket to our internal issue tracker to be prioritized. We'll let you know when we've got more to share.


  2. Richard-Day

    My individual account is collaborating with a team. For work on my repos I'd like email routed to my account address. For work on their repos I'd like email routed to both my account address and their address (I specify which), or perhaps just theirs. I want a simple, team-level Bitbucket "team email" solution that'll make that happen.

  3. Manuel Wahle

    I second that and extend it a bit: it's not just about notifications but about the email associated with a repository. In the raw commit view of online edits my primary email is visible. I don't like that my private email is leaked to my company if I have private and company repositories. Neither is it cool that all emails go to one address.

  4. Stephen Handley

    +1 for letting users associate email address with each team

    I sign up for bitbucket with my personal email address

    Later I join some teams

    TEAM 1) Joe's Barf Shack
    TEAM 2) Joe's Puke Lounge
    TEAM 3) Joe's Food Hospital

    By default all my notifications still go to my primary email:

    Then, for Teams 1 and 2 I get org-specific email addresses, and so for those teams I set specific email addresses:

    TEAM 1) 
    TEAM 2)

    Now for the result

    1) I get emails at
    2) I get emails at
    3) they still go to because I haven't set a specific address for that team 
  5. Adriaan Peeters

    Any updates on this? The perfect solution would be to associate an email address with each team but per repository address would also solve the problem while allowing different use cases.

  6. Sylvain Minjard

    Why not both? By default it would take the e-mail attached to the repository, then the e-mail attached to the team that owns the repository and then your primary e-mail address (from the most specialized one to the most global one).

  7. Log in to comment