A little background on how the dashboard works. Think of each project group as a Cartesian join of all the environments available to a project. For example, I have this project with the following lifecycles.
The dashboard will show all the environments for this project. Not just the ones in the default lifecycle.
If I remove an environment from the lifecycle
The dashboard will be updated to reflect that.
In addition, it will go through and add all the environments for all the channels for all the projects in each project group. If I move that project group up to the default project group you’ll see the development environment appears next to it, but it is empty.
To remove an environment from a project group, you’ll need to remove it from all lifecycles used by all the projects in that project group. Removing an environment from a lifecycle will not affect any releases. If a release went out to that environment it still is there. What you’ve changed is how releases are promoted going forward along with what appears on the dashboard.
If you don’t want to remove an environment from a dashboard. You can customize the dashboard by clicking the configure button in the top right corner. In this case, I only want to see test and production.
Which results in:
But this is a per person setting, not a global setting.
In regards to your specific feature request:
it’s would be useful to clear a Project/Environement deploy when auto-deploy Triggers are in play and a new environment is not ready for auto-deploys.
Our UX team is looking at how to make dashboarding better. I’ll raise this as a use case with them, but there is no guarantee it will be done, nor a timeframe if/when that’ll happen. I think it could be useful, but the question we always have to ask ourselves is, how many of our customers will find this useful and how many have been asking for it? This is the first time I’ve heard of a request, so the chances are fairly slim it’ll be picked up.