I work on a project that has its codebase spread across many git repos.  Bamboo only maintains branch awareness for the plan's default repository, any other repos added to a build plan require the branch to be set manually.  We currently use plan variables to ease the maintenance required for this, by setting the branch name of linked repos to a variable and then setting and overriding that variable in each plan. The maintenance required could be further significantly reduced if build-specific variables (specifically bamboo.shortPlanBranchName) were made available during the revision check stage of a plan, which should eliminate the need to override the variables for every created branch.  Under current behavior, it seems that when checking revisions the plan variables are usable during the revision check but build-specific variables are not, so attempts to use bamboo.shortPlanBranchName as the branch in the current software result in plans immediately failing due to the revision check being unable to find the branch (since it wasn't actually set).