[GH-ISSUE #5840] [feature]: Ability to link/associate a default Environment with a Collection #2287

New issue

Open

opened 2026-03-16 23:51:34 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 23:51:34 +03:00

Owner

Originally created by @Trishadring on GitHub (Feb 5, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5840

Is there an existing issue for this?

I have searched the existing issues

Summary

would like an option in the Collection Settings (or the "Edit Collection" modal) to select a "Default Environment."

Behavior:

When I click on a collection or a request within that collection, Hoppscotch should automatically switch the active environment to the one associated with that collection.
If no default is set, it should just keep the currently selected environment.

Describe alternatives you've considered

Currently, I have to manually use the environment dropdown every time I switch collections. Another alternative is using "Collection Variables," but these don't replace the need for environment-specific secrets (like API keys or base URLs) that change between Dev, Staging, and Prod.
Additional context

This would greatly improve the user experience for developers managing multiple projects within the same Hoppscotch instance. It ensures the "Context" (Collection + Environment) is always in sync.

Why should this be worked on?

When switching between different collections (e.g., switching from a "Payment API" project to a "User Management" project), I have to manually change the Environment in the top-right corner every time.

If I forget to switch the environment, the requests fail or, worse, I accidentally run a request against the wrong environment. It is time-consuming to manually toggle this every time I click a different collection in the sidebar.

Originally created by @Trishadring on GitHub (Feb 5, 2026). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5840 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary would like an option in the Collection Settings (or the "Edit Collection" modal) to select a "Default Environment." Behavior: When I click on a collection or a request within that collection, Hoppscotch should automatically switch the active environment to the one associated with that collection. If no default is set, it should just keep the currently selected environment. Describe alternatives you've considered Currently, I have to manually use the environment dropdown every time I switch collections. Another alternative is using "Collection Variables," but these don't replace the need for environment-specific secrets (like API keys or base URLs) that change between Dev, Staging, and Prod. Additional context This would greatly improve the user experience for developers managing multiple projects within the same Hoppscotch instance. It ensures the "Context" (Collection + Environment) is always in sync. ### Why should this be worked on? When switching between different collections (e.g., switching from a "Payment API" project to a "User Management" project), I have to manually change the Environment in the top-right corner every time. If I forget to switch the environment, the requests fail or, worse, I accidentally run a request against the wrong environment. It is time-consuming to manually toggle this every time I click a different collection in the sidebar.