Open cynicaljoy opened 5 years ago
@cynicaljoy We understand this can become a real pain. Our recommended way to get around this is to use different workspaces contextually for different projects/APIs/teams. While this might not be exactly what you are asking for, we've personally found to be quite effective.
Having said that, we're actually working on something that'll enable you to filter the environments from the ones compatible with the collection/request and to automatically select the most appropriate one. No ETA yet, but fingers crossed!
Would be happy to hear more details about the exact problems that you face while selecting environments (with examples hopefully). It helps us design a better experience.
+1
Is your feature request related to a problem? Please describe. Many of my Environments are not compatible with all of my Collections. My select Environment dropdown is (partly self-inflicted) cumbersome to navigate.
Describe the solution you'd like I would like to be able to associate Envionrments per Collection and my Postman UI to only show Environments that are associated with my selected Collection.
Additionally, I would like to be able to configure Postman to automatically default to a given Environment by Collection.
Describe alternatives you've considered None
Additional context I'm using Collections individually as well as part of a Team. The ability to associate Environments/Collections should be applied for the Team.