Pre Bamboo 2.0, You used to be able to specify the following in the depot field and Bamboo would quite happily sync to and collect changes for that label. There have been a number of changes since 2.0 which have broken this functionality.

//client/depot/...@myLabel

• When doing a first checkout bamboo has no vcs revision number so automatically assumes you want to checkout to head and appends "#head" to the end of the command. Obviously this will cause confusion - does it check out to head or to the label?
• Collecting changes has recently been changed to use the @ notation to reduce the amount of information required, thus you end up with strings looking like "p4 -c client changes //depot/...@failedLabel@278,@now" which is syntactically incorrect.
• Subsequent checkouts. I imagine these will also cause problems, however i am currently unable to determine exactly what. This also uses the @ notation to specify a revision number to sync to

Pre 2.0 this label functionality existed by default - we never put anything in to try and get it working. Moving forward we have two options.

1. revisit each use case to allow for the above depot definition
2. look at handling of labels completely seperately (similar to the way we do tags/branches for svn) and look at using e.g labelsync instead