[GH-ISSUE #4567] [bug]: Reordering requests within a collection does not save/restore it correctly #1680

New issue

Closed

opened 2026-03-16 21:22:06 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 21:22:06 +03:00

Owner

Originally created by @prathamesh-gharat on GitHub (Nov 27, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4567

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When I drag-drop and re-order the requests in a collection, I get a message saying "Request Order Updated" but after refreshing the page the expected order is not restored.

I am using the latest docker AIO image at the time of writing this.

There are no errors in console.
The HTTP response for the re-order request is as follows
{"data":{"updateLookUpRequestOrder":true}}

Steps to reproduce

Create a collection.
Add 2 or more requests to it.
Drag and drop a request to re-order position of a certain request.
Refresh the page.
Check if the request is in the expected position.

Environment

Production

Version

Self-hosted

Originally created by @prathamesh-gharat on GitHub (Nov 27, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4567 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When I drag-drop and re-order the requests in a collection, I get a message saying "Request Order Updated" but after refreshing the page the expected order is not restored. I am using the latest docker AIO image at the time of writing this. There are no errors in console. The HTTP response for the re-order request is as follows ```{"data":{"updateLookUpRequestOrder":true}}``` ### Steps to reproduce 1. Create a collection. 2. Add 2 or more requests to it. 3. Drag and drop a request to re-order position of a certain request. 4. Refresh the page. 5. Check if the request is in the expected position. ### Environment Production ### Version Self-hosted

kerem

2026-03-16 21:22:06 +03:00

closed this issue
added the
bug

need testing
labels

kerem commented

2026-03-16 21:22:22 +03:00

Author

Owner

@prathamesh-gharat commented on GitHub (Dec 10, 2024):

Just a note: Updated the Hoppscotch AIO container to v2024.10.2, hard refreshed the browser, tried to re-order a request, refreshed page, the order of the request within a collection/folder is not retained.

@prathamesh-gharat commented on GitHub (Dec 10, 2024): Just a note: Updated the Hoppscotch AIO container to v2024.10.2, hard refreshed the browser, tried to re-order a request, refreshed page, the order of the request within a collection/folder is not retained.

kerem commented

2026-03-16 21:22:27 +03:00

Author

Owner

@KulikovaAnna commented on GitHub (Mar 4, 2025):

Hi! I start using hoppscotch and I get the same error. This complicates the work, you need to change the order of queries before each collection launch

@KulikovaAnna commented on GitHub (Mar 4, 2025): Hi! I start using hoppscotch and I get the same error. This complicates the work, you need to change the order of queries before each collection launch

kerem commented

2026-03-16 21:22:32 +03:00

Author

Owner

@ariados26 commented on GitHub (Mar 4, 2025):

Faced the same problem

@ariados26 commented on GitHub (Mar 4, 2025): Faced the same problem

kerem commented

2026-03-16 21:22:37 +03:00

Author

Owner

@jamesgeorge007 commented on GitHub (Mar 7, 2025):

Hi, this is fixed in the latest release. Please let us know if the issue persists.

@jamesgeorge007 commented on GitHub (Mar 7, 2025): Hi, this is fixed in the latest release. Please let us know if the issue persists.