Sure, maybe it has been fixed in 6.1.0 but is not working in version 6.7.1.

calin.pirtea 6.1.0 is going to be released in few weeks, no exact date has been set though.

Yay.

About time... Are you releasing it today?

In Bamboo 6.1 we are adding an option to apply the version naming scheme to all the branches.

We are managing our version numbers by using the Inject Bamboo variables task. We have different naming logic depending on the branch. For example, we append -pre{build.number} if the build is from a feature branch. We assumed the release versioning variables we were using would work across all branches. It is surprising that the feature doesn't work as explained in their documentation: https://bamboo.corp.alkamitech.com/deploy/config/configureDeploymentProjectVersioning.action?id=28803078. This should be considered a bug, not an improvement. Please fix Atlassian.

Watching this thread for a good solution but in the mean time my hack is just to clone the deployment plan for every branch that we want to build/release.  It is horrible an time consuming and an absolute waste of resources to manage/do but that's what Atlassian is giving us.

What you'll have to do is take your "master" deployment and clone it.  On the clone, click the "edit the build plan" and change the branch to the custom plan branch you want. When the build fires, this branch deploy should fire and you will get a properly named/versioned release. 

Word of warning though, if you make a change to the master deploy project, you will need to manually apply that change to all of the cloned deploy projects.  We're trying to keep branch deploys to a minimum but we currently have 5 branches that get deployed and 1 master.

Bump. I know "bump" is bad, but given that this has been open since 2014, and we're now in 2017, perhaps renewing our interest in this issue by commenting on it will get the Bamboo team to pay attention to it...

We need to created releases from plan branches. The release name should be the release version generated by Gradle

For this I wanted to use an Inject Bamboo variables task getting the version from a properties file and saving it to a Bamboo variable. This does not work for plan branches

Can we get some feedback about this Atlassian? Also being discussed here: https://jira.atlassian.com/browse/BAM-14891

Any users with a workaround?

It's important for us to have all our release names tagged with the build numbers...

Forcing the naming convention for branches does not scale well at all. Now we have to rethink our procedures, archive structure and implement (more) workarounds to address small but significant restrictions in Bamboo.

Can you please let us know if you have planned to implement this any of the releases yet ?