Unexpected commits from other branches in Bamboo deployment notifications

Question

Hi Atlassian Community,

I'm investigating how Bamboo calculates the commits and Jira issues displayed for a deployment release, as we're seeing behavior that we don't fully understand.

When we deploy a release, both the deployment details in Bamboo and the deployment notification email show commits/issues that appear to come from branches unrelated to the deployed release. Since the email mirrors the deployment report, it seems the underlying deployment report itself is including these commits/issues.

Our expectation was that a deployment release would display only the commits and Jira issues associated with the deployed release. Instead, Bamboo appears to be performing a comparison between deployment versions, which can include commits from other branches and makes it difficult to determine exactly what was deployed.

This behavior started appearing this year.

Could someone help clarify the following?

* How does Bamboo determine which commits and Jira issues are included in a deployment release?
*  and Jira issues are included in a deployment release?
* Is it expected for commits from other branches to appear in the deployment report if they are part of the comparison between deployment versions?
* Is there any configuration that controls whether Bamboo displays a version-to-version comparison versus only the commits and Jira issues associated with the deployed release?
* Were there any recent Bamboo changes that modified how deployment reports, deployment notifications, commits, or Jira issues are calculated?

Any documentation explaining how Bamboo builds the deployment release report would be greatly appreciated, as we're trying to determine whether this is expected behavior, a configuration issue, or a recent product change.

Thank you!

Francisco Guzman_33ui5d · Answer

Thanks for you answer,

For this particular project is an standalone project with different git branches to be deployed on different environments.

So the deployment project already have all this configuracion per target git branch and plan branch as you can see in the follow image.

The issue is that the deployment notifications show all the commits from the Git repository, including every change made between the previous deployment and the current one, instead of showing only the commits for the version being deployed.

as you see in the image above is showing 137 issues and 77 commits related and for this deployment there was only one change for one issue just for the git branch that this version was deployed this is something that confuse the User who open this kind of notifications.

In addition, the deployment release report compares the changes between releases instead of showing only the changes associated with the version being deployed. This is something that didn't happen before in the deployment notifications.
When we clic on 137 issues

let me know if you need more information

Ajay · Answer

Hi @Francisco Guzman

Can you verify if your deployment project is linked to the correct build plan (not a plan branch). Go to Deployment project > Edit > Build plan and confirm it points where you expect.

If you're using plan branches with "all branches" detection, narrow the repository configuration to track only the branch you actually deploy from.