Allow multiple dashboard configurations, and users can switch between them.
It would be great if you could save multiple dashboard configurations (as opposed to just the single one) and then switch between them.
The reason behind this suggestion is that we have so many different projects and customers (each customer with their own set of environments) that when you want a view thats in the context of a particular customer, you have to constantly re-configure your existing dashboard to filter out all of the noise. It would be easier to define the dashboard configuration once for a particular customer, and then simply switch to it.
If you really wanted to impress, you could enable users to flag their dashboard configurations as "shared" - in which case other users could see the same configuration in their list of dashboard configurations. Perhaps only the "owner" of the shared dashboard would have the rights to edit it.
Another improvement to that, would be the ability to create a new dashboard configuration via cloning an existing one.
I’ve reset the status of this suggestion, as the requirement described is for multiple dashboard configurations per-user, which Octopus does not currently support. Apologies for the misunderstanding.
Keith O'Brien commented
Having multiple saved dashboards for identifying what you actually need to see makes good sense.
H. Wäscher commented
+1 Allow multiple dashboard configurations, and users can switch between them.
we have a lot of project groups and enviroments, the current UI is horrible, i see more scrollbars than projects groups. It's incredibly frustrating to work with octopus, multiple dashboard would at least make it easier.
Patrik Lindstrom commented
In what version was this implemented? I cant see it in the current version. Am I missing something? Can you save different dashboards like D1, D2 , and switch between them now?
Nathan Prado commented
+1 it would be great to have the ability to make deployment information visible even on the granular level of project variables
Ganesan Rajaraman commented
We have numerous projects too and same person needs to look at different set of logically grouped projects for different purposes (patch release, upcoming release etc). I was disappointed that this is not possible. This will be a great addition.
PS: BTW, what is the deal with not sorting "Excluded" list under "Configure your dashboard"? The groups seem to be in alphabetical order but the projects underneath them are not.
UI 101: Anything presented to the user must be sorted in some obvious way. "Configure your dashboard" fails in this area.
Albert Wang commented
Currently we have team members working on deployments in different environments for a common set of projects. This requires that each team member set up their dashboards separately and asynchronously.
Keeping dashboards synchronized is time consuming and error-prone.
This idea would save us a lot of time and frustration.
B Au commented
One of the main selling point with Octopus is the great user interface. This extra change would make life run smoother/quicker for my team.
Rosti Grigoriev commented
We also have a lot of projects and environments. The dashboard became very busy and specifying filtering every time we want to concentrate on different areas is very inconvenient.
I understand that the Octopus team works on a lot of interesting features and it's difficult to allocate time for something that may be perceived as "non-essential" but usability is very important too.
Patrik Lindstrom commented
I would also like the ide of team dashboards. So we could set up a dashboard eg for all scrummasters. Eg: All projects to be released in next release slot.
Mark Nash commented
I love this idea, was going to add it myself
We have currently got loads of environments for a customer as we are migrating them to a new set of environments.
This means that if you want to view half of the environments on the dashboard tou have to constantly scroll accross.
It would be really good if i could save some dashboards showing me consisely what i want to see.
Another improvement idea could be for an overal environment icon, where if any project was in a failed state it would change the environment icon to indicate this.