mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #5807] [question]: Importing pre-request & test scripts from Postman #2270
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#2270
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 @rklec on GitHub (Jan 28, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5807
Is there an existing issue for this?
Summary
I have imported a postman collection and environment in the same run, and I got this screen:
Why should this be worked on?
Postman is likely the major competitioner, so having a seamingless way to import everything is very important so users can easily migrate away.
Also I found no such issue about that topic, which kinda surprised me, but maybe I missed one?
I only found https://github.com/hoppscotch/hoppscotch/issues/5477 but that is not about the import.
HoppScotch v2025.2.2
@jamesgeorge007 commented on GitHub (Jan 29, 2026):
Hi, support for importing scripts from Postman collections was added in the v2025.10.0 release via #5417. It is recommended to upgrade to the latest version. Documentation can be found here.
Please note that this feature is experimental and requires opting into the
Experimental scripting sandboxoption via settings.Closing this issue. We welcome your feedback, which will help shape the next generation of Hoppscotch scripting. Feel free to share it via the RFC #5221.