We are also affected by this after upgrading to 6.10.4.  Any updates on a fix for this?

We are also affected by this issue with Bamboo 6.8.1. We are going to use the workaround suggested by Jonathan Lynch for now, but it would be nice if this could be fixed soon.

Update: I am working around this issue by awk'ing the shortPlanName out of the planName. The branch build doesn't seem to mess up the planName, only the shortPlanName.

+1 on this issue. This is messing up my branch builds. Would rather not work around it by introducing an additional variable, as this makes it more difficult to clone plans and have the clone still work.

I just ran into this... I wanted the Plan name ... and got the branch name.

And yes, we are using branch builds ... but so what ... "branch name" ... "plan name" ... provide what is advertised.

Love is a strong word, but I do have a mild affection for it. It may not be a bug in the 'broken' sense of bug, but it is, in my opinion, a bug in the sense of being non-intuitive/unexpected behaviour. There is already a variable that returns the branch name, so the plan name should always return the plan name.

Any love for this issue? I was wondering if this was really a bug and not by design for some reason....

So a couple workarounds:

1) Set a variable in the Build Plan that can be referenced instead of shortPlanName

2) Set the Build Job's name to the desired value, then reference bamboo_shortJobName

These are not ideal, but both will get the job done for now. If this is a bug, it needs to be addressed at some point.

Affects 5.15.4. This is a little bit of a pain for me too. If I wanted the branch name, I'd've asked for it with the branchName variable.

Affects version 5.14.0.2