Thank you for your reply and details, only this is not what I was looking for I suppose.
Now the default lifecycle is also adjusted for all the projects when I’m adding an environment. Maybe I am misunderstanding it a bit when using those lifecycles, because I can now just use the default one because it is added there now as well.
Let me explain it a little bit more.
All our projects are using a default lifecycle of test, acceptance and production. Now I got a question from a user to have a training environment with it as well. But I do not really want to show this environment for all the projects as not all the projects needs this training environment.
Also we are still not sure if we are going to have a dedicated training environment. Rather maybe want to deploy it together on our acceptance environment as a separate website with it’s own database. What are your thoughts about this? Have you ever seen such configuration?
Please let me know.