mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 08:45:58 +03:00
[GH-ISSUE #5981] [bug]: Renaming a duplicated request reverts to the original name upon saving #2350
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#2350
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 @synstin on GitHub (Mar 13, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5981
Is there an existing issue for this?
Platform
Desktop App
Browser
Chrome
Operating System
macOS
Bug Description
Description:
When I duplicate a request and attempt to rename it, the new name appears to be applied in the UI. However, as soon as I click the "Save" button, the request name immediately reverts to its previous name (the duplicated name) and is saved with that incorrect name.
Steps to Reproduce:
Deployment Type
Hoppscotch Cloud
Version
26.2.1 (26.2.1)
@AbyJms commented on GitHub (Mar 13, 2026):
Hi, I’d like to work on this issue.
@AbyJms commented on GitHub (Mar 13, 2026):
Hi, I tried reproducing this issue on the latest main branch locally but couldn’t reproduce it.
Steps I followed:
The renamed request persisted correctly and did not revert.
Tested on:
• Windows (local dev setup)
• Brave (Chromium-based)
This might be platform-specific (macOS) or already fixed in newer versions. Happy to re-test if needed.