Unexpected commits from other branches in Bamboo deployment notifications

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?

1. How does Bamboo determine which commits and Jira issues are included in a deployment release?
2.  and Jira issues are included in a deployment release?
3. Is it expected for commits from other branches to appear in the deployment report if they are part of the comparison between deployment versions?
4. 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?
5. 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!