It will only show the commits if there are commits since the last build in the branch/trunk you are building from. (Your problem may very well be something that is not this simple - I know you said code was committed. Verify this occurred in the branch/trunk you are building).
For example if I run a build it will pick up any changes since the last build (can be viewed by the bamboo.repository.previous.revision.number versus the bamboo.repository.revision.number - put in a scripted echo to display the two variables in your log file.)
If I run the build again before any new changes have been committed the list of changes will be empty.
I'm guessing this is not your issue but thought I'd throw it out there. You can also run customized and specify an earlier revision that you know is included in the branch you're building from.
Also take the previous build's revision number and the current builds revision number (or HEAD etc.) and run a manual log command against your repository to identify the specific commits in your repository. This will provide validation of exactly what should have changed (and displayed) in the second build. I'd start there. Figure out what it should say then you have a position to approach Atlassian with in a support ticket that would help them help you. That would verify that indeed there is a discrepancy between what bamboo is showing and what it should be showing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.