Allow me to choose which environments a project uses / per project environments
We have multiple projects being deployed to different servers in heterogeneous environments. Some are just test-production, others are dev-test-staging-production. The projects often have completely separate environments.
It would be beneficial to be able to either choose which environments a project can deploy to, or to be able to set up per-project environments to be able to keep the same names for config transforms. (ex. "Web.Test.cfg" instead of "Web.Test-Product1.cfg")
Currently the Dashboard is also very "cluttered" with empty boxes due to those environments not being in use for certain projects.
Lifecycles are the way in which users can define what environments are used in what projects
Lifecycles don't solve the problem with the OP's last sentence: "Currently the Dashboard is also very "cluttered" with empty boxes due to those environments not being in use for certain projects."
Which still holds true to the latest release v2018.10.0. Hiding all environments that aren't included in the lifecycles for any project in the project group would be a big plus in UX.