mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #3736] [feature]: Collection-wise environment variables #1296
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#1296
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @shibilpk on GitHub (Jan 9, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3736
Originally assigned to: @nivedin on GitHub.
Is there an existing issue for this?
Summary
We need set variable for collection itselfto
Why should this be worked on?
If working on more projects. Sometimes its easy to manage variables if there option to set variables for collection. In that case, we need to create less environment.
@GauthierPLM commented on GitHub (Jan 15, 2024):
My team has around 30 to 40 collections in our team space, with one collection for each micro service. As we have many variables that are specific to a given collection, it does not make sense for us to put them in the environment, as the number of variables would grow to an unmanageable number.
Having collection-level variables like what Postman offers would allow us to properly manage our collections / variables with the granularity we need. This is the last blocker we identified to switch from Postman to Hoppscotch.
@liyasthomas commented on GitHub (Jan 15, 2024):
Thanks for your feedback, we'll look into adding this to the roadmap.
@GauthierPLM commented on GitHub (Jan 24, 2024):
@liyasthomas is there any place to see the roadmap / priority you'd give to this feature?
@weinull commented on GitHub (Apr 7, 2024):
looking forward to this feature
@m-amiri commented on GitHub (Jun 30, 2024):
same issue
@BoscoDomingo commented on GitHub (Sep 16, 2024):
I echo the rest. It's the missing bit to be able to replace Postman
@Pelagoss commented on GitHub (Oct 22, 2024):
Same problem, please add this feature
@ankitgirase commented on GitHub (Dec 24, 2024):
@liyasthomas can you please share progress for this feature. We are making transition from postman to hoppscotch and only this one feature is limiting us, your response will be valuable for us.
@ankit-girase-zw commented on GitHub (Jan 10, 2025):
@GauthierPLM did your team shifted to hoppscotch from postman ? If yes how did you managed collection variables ?
@GauthierPLM commented on GitHub (Jan 10, 2025):
@ankit-girase-zw because this feature was central in our workflow, we decided to stick with Postman unfortunately.
@lsdgem commented on GitHub (Jan 17, 2025):
I strongly agree with all the other people in this thread. This is genuinely the only reason we can not switch from Postman to Hoppscotch
@Aurgil commented on GitHub (Feb 17, 2025):
We need this feature too to use Hoppscotch.
@carterclark commented on GitHub (Mar 27, 2025):
Would love for this to be added
@ygg-shibil commented on GitHub (May 7, 2025):
@liyasthomas Any Update on this Feature? Please give an update
@m-amiri commented on GitHub (May 24, 2025):
any updates? 👀
this is a key feature to migrating form postman to the Hoppscotch.
@liyasthomas
@faritor commented on GitHub (Jul 22, 2025):
Hi,@liyasthomas ,
in which version will this rough plan be implemented, or is there an expected time? this is one of the key points that prevent me from migrating as a whole
@mcules commented on GitHub (Jul 28, 2025):
This is the feature I miss the most. It would make perfect sense to be able to store variables under collections or even directly within individual folders. I use this functionality extensively in Postman and hope it will be available here soon.
At the moment, this is the only thing keeping me from fully switching to Hoppscotch.
@mashmex commented on GitHub (Jul 30, 2025):
Hi together,
This feature is very important, especially when migrating from other services such as Postman. Since you don't always create separate workspaces for a project/customer. In Postman we were able to set variables on collections there, it would be important for this feature to be available in Hoppscotch as soon as possible.
Thank you.
@liyasthomas commented on GitHub (Jul 30, 2025):
We’ve begun working on this feature request. We apologize for the delay. We expect this feature to be shipped soon.
@jamesgeorge007 commented on GitHub (Aug 28, 2025):
Hi, the v2025.8.0 release is now live and includes support for collection variables, closing this issue. Please feel free to reach out if you have any questions.