Nested Environment Domains

[andrewhamon]

trafficstars

So a problem I keep running in to is environments that depend on other environments.

For example, I usually have a server domain that has the endpoint info for several different environments (dev, staging, production).

Then I have a user domain with several different users. The problem is, some users exist on some servers but not others. It seems silly to be able to select a user that depends on a server different than the currently selected environment in my server domain.

It would be great if there was some sort of nested domains/environments. So each of my server environments could have its own set of users, and I could only select users from the currently selected server.

[mittsh]

@andrewhamon Thanks for the feedback/input. We are running into a UX & product choice for environments. Many users are confused in the way environments work because of the various domains, they expect a single dropdown to select environments. And on the other side, we know that we can give more power to seasoned users by adding nesting as you suggested.

Btw, the UI for editing environments is going to change to a nicer and more user friendly view in the upcoming version.

Though, we're clearly keeping this idea of nesting in mind (we had requests for it already before). If we do it, we will make it a way to it's not making the existing UI heaver.

And also, we need to find the time for it – so many other great features to come :)