Premisses:

• Bamboo 4.4.5
• Git repository being checked out
• Git committer alias associated with a Bamboo User

Steps to reproduce:

• Create a new plan
• Make it checkout from a Git repository branch, it can be the master branch.
• Add a second task that will make the build fail (e.g., I added a JUnit Parser task, but I don't have any JUnit test results to parse, so it will fail).
• Don't enable the plan yet - you need to configure notifications first - but you can click on the Create button.
• After creating the plan, go to the Notifications tab, and configure the plan to send a notification for the event Failed Builds And First Successful, having Committers - Users who have committed to the build as Recipient Type.
• Click on the Action cog icon and enable the plan
• Run the plan manually.
• It will fail as expected, but no notifications arrive at the committer inbox.
• Remove the failing task (the JUnit Parser, in my case), and run the plan again.
• It will succeed, but no notifications arrive at the committer inbox either.

The exact same steps work if I choose to checkout from a SVN repository (i.e., the committer receives a notification), so the problem seems to be conditioned to when using Git as repository type.

No errors are written in the log files.