Currently, If a new branch is created as disabled, it has no baseline to determine if a change is in fact, new. So when enabling the branch, Bamboo skips the first detection.

When creating the Branch there's a checkbox and a little explanation below:

"By selecting this option your branch will be available for building and change detection straight away"

However, it's not clear that for change detection to be enabled again, it needs to manually run the branch at least once after it's enabled.

The current solution would be enabling Automatic branch management instead of Manually, but it does not meet the requirements for some users, thus, requiring the manual creation of branches.

Steps to replicate

1. Create a branch in Bamboo (as disabled) -> needed to change variables in the source code so it does not automatically run the first build
2. Manually enable it
3. Make a change in the repo to trigger the build
4. Merge to the default branch (Develop)

Results:

Only the default branch kicks off

Expected results

• Both Default branch and new branch (manually enabled) should kick off
• Have the ability to choose a baseline from existing branches (or use the default)
• When that first change is detected, the ability to assume there is a valid change in there and trigger a build