mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #4612] [bug]: Import Collection contains Untitled Requests #1706
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#1706
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 @dansmitt on GitHub (Dec 12, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4612
Is there an existing issue for this?
Current behavior
When I import for example a Postman collection, the requests looks like this:


instead of:
It only happens in shared workspaces.
Appearing in Cloud and Local (Windows)
Steps to reproduce
Environment
Production
Version
Local
@dansmitt commented on GitHub (Feb 4, 2025):
Had a look to the export from Postman and I was able to figure out that it only happens if you work with examples in Postman, so that the response section is filled.
Example:
@tjh19971228 commented on GitHub (Feb 21, 2025):
had you solved this problem ? @dansmitt
@dansmitt commented on GitHub (Feb 21, 2025):
Nope. You need to manually remove the examples from the import json. Id prefer something like that it will be ignored during the import
@musfiqtf commented on GitHub (Jul 6, 2025):
Still facing this issue in shared workspace. How to fix it?
@dansmitt commented on GitHub (Jul 10, 2025):
@musfiqtf have a look to my workaround.