I don't think this is currently possible using existing dependencies mechanism or predefined triggers.
However, build triggers are now pluggable (since ~5.8 I think) and there might be a plugin that does what you are looking for. Unfortunately I don't know of any. And I'm not sure if implementing custom triggers in Bamboo is documented.
An alternative solution would be to add the rollback as a stage in the same build plan, if it's not very advanced. You could add some conditions to all tasks if they should or should not be executed (e.g. all logic can be done within a script task, which could just read a variable or look through artifacts produced by previous stages and decide what to do). But this seems like an ugly workaround, not what you're trying to achieve.
You can try plugin I created to show how to create new trigger. It's not tested nor supported officially by Atlassian. Look at https://bitbucket.org/chystoprudov/bamboo-failtrigger-plugin/overview.
I'll be happy if it will solve your use case
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot