Thanks for the feedback. It's definitely a good idea.

We'll be revisiting the notifications in the near future (to add more flexibility in this area) and we'll keep this in mind

Cheers

Mark C

It would be nice to select the list of users who had modifications which triggered the build be the ones getting the email. Right now, for every project, the email list would basically have to be to our entire group – even though a bunch of them may not really care about that project. However, its much too cumbersome to manually enter in a distinct list of user names for a particular project (see BAM-680).

I notice that you can link a user's name to the repository (i.e. SVN name) . And since you have the user's email from the user definition, it shouldn't be too bad to have a notification go out to the change list modifiers. This would go a long way in making the product more friendly to developers who might be wondering why they got an email on a build that they don't care about. it would also keep the quantity of mail to a minimum and not train the users to ignore the email when, in fact, it really might be telling them something important to them.

These are definitely all great suggestions when we revisit our notification schemes.

Unfortunately, the 'near future' would be something post release 1.0. We are currently in 1.0 beta now and the final version will be coming out very soon. We should hopefully be able to get to notifications soon after that.

Regards,
Edwin

Right now we have the email getting sent to a mailing list so people are learning to ignore the Bamboo email because it doesn't apply to them a lot of the time. This defeats the purpose of having a tool like this.

The more directed the email is, the more useful it is. People would then feel empowered and responsible for fixing things.

Yes, this was implemented in Bamboo 1.1. Thank you for pointing it out.

I will now resolve this issue as fixed.

Cheers,
Ajay