James, thanks for that! For some reason I never found that option! I agree the UI is far from consistent. There's some weird UI and feature set differences between build plans and deployment projects.

Martijn, I agree with you on the requirements, but you*_ can_* clone deployment plans. If you go to edit a deployment project, you can clone the whole thing from the drop down in the upper right corner, the one with the three dots. Clone project is right there between Edit project details and Delete project. No idea why this UI is so different to that for the Build projects, but it certainly does what you'd expect.

While the plugin workaround is useful... and I do consider it a workaround... I'm truly amazed about the huge, gaping hole in the feature set of deployment plans left by Atlassian that should be fairly easy to fix.

Specifically two items stick out:

• Not being able to clone deployment plans
• Not being able to set requirements on a deployment plan

The cloning feature already exists for build plans and works nicely. It should not be difficult to do the same for deployment plans. Slightly different screen and slightly different set of DB fields to clone.

The requirements feature not being there really boggles the mind for me. We have this annoying "agents" button in the environment config screen, but not a very much needed "requirements" button. Apparently the feature isn't that hard to do since we have that plugin that does it, so why not have that button in the environment config screen??

While you're at it, please, please, please remove the "agents" button or at least allow us to turn it off. It has already caused havoc on our systems because a user decided to dedicate all of our agents to his deployment. I know we can revoke his permissions to edit the deployment plan, but I don't want to do that since the whole "dedicate agent" feature is not exactly properly explained, nor even very necessary.

We need our windows agent. How do I install the requirementtask in the SaaS (cloud) offering?

Jules, if you're not using the Windows image at all, you can also disable it on image config page.

If you are looking for this feature - you can use the following plugin to add requirements to deployment environments.

https://marketplace.atlassian.com/plugins/com.atlassian.bamboo.plugin.requirementtask/server/overview

Please implement this. For some reason the Windows stock image is the default, where our deployment is Linux based.

Agree with those above. Having to tie agents to deployment projects means we have no choice but to segregate a group of agents for this purpose - taking them out of consideration for other activities.

Agree with @richard.beers620876970. Please re-evaluate the priority of this ticket.

(@spittet are the PM for Bamboo Cloud?)

For cloud bamboo, this is IMHO a important feature to have.

This is my use case:

I now work with dedicated images. That works. For both build plans and deploy plans.

I would like to be able to use capability on images, and requirements on plans. This works fine with build plans.

If I use it on my build plan, it seems logical to me I also do the same with deploy plans. This seems not possible.

This forces me to use a dedicated image for the deploy plan, however this now prevents me from using this same image by the build plan through capabilities/requirements mapping.

Therefore I now also need to use dedicate image to force the build plan to use it. This is much less flexible then using requirement/capabilities.

If I edit a deploy plan I can select an agent/image in "other environment settings", if I do so, the text displays: "Dedicate specific agents or image configurations to execute all deployments for this environment. If you do not assign an agent to this deployment, one will be chosen at run time according to standard requirement/capability mappings."

So please implement it, your text is already ready!