starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #4976] [bug]: Automatic Request Reordering Issue #1889

New issue

Open

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

kerem commented

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

Owner

Originally created by @rajkumar-cp on GitHub (Apr 9, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4976

Is there an existing issue for this?

I have searched existing issues and this bug hasn't been reported yet

Current behavior

Requests within a collection are reordered incorrectly after performing a series of actions including exporting, importing, moving, and refreshing the page.

Steps to reproduce

Create a collection with the structure shown in the attached screenshot.
Export the collection.
Import the collection back into the workspace.
Move "Child 3" to the position of "Child 1".
Refresh the page.

Expected Result:
The order of requests should remain as manually rearranged.

Actual Result:
Requests are automatically reordered incorrectly after refreshing the page.

Logs and Screenshots

Environment

Production

Hoppscotch Version

Self-hosted

Interceptor

Browser - Web App

Browsers Affected

Chrome

Operating System

Windows

Additional Information

No response

Originally created by @rajkumar-cp on GitHub (Apr 9, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4976 ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Current behavior Requests within a collection are reordered incorrectly after performing a series of actions including exporting, importing, moving, and refreshing the page. ### Steps to reproduce 1. Create a collection with the structure shown in the attached screenshot. ![Image](https://github.com/user-attachments/assets/552d511c-32f5-4f04-96a2-e602ad45c168) 2. Export the collection. 3. Import the collection back into the workspace. 4. Move "Child 3" to the position of "Child 1". 5. Refresh the page. Expected Result: The order of requests should remain as manually rearranged. Actual Result: Requests are automatically reordered incorrectly after refreshing the page. ![Image](https://github.com/user-attachments/assets/7241216c-06c2-4e3e-83b2-cfc85541b5bb) ### Logs and Screenshots ```shell ``` ### Environment Production ### Hoppscotch Version Self-hosted ### Interceptor Browser - Web App ### Browsers Affected Chrome ### Operating System Windows ### Additional Information _No response_

kerem added the

bug

need testing

labels

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

kerem commented

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

Author

Owner

@g3Bg2 commented on GitHub (May 8, 2025):

@rajkumar-cp

Have you been able to check the exported json? Is it unstructured?

Cannot replicate it on my end.

@g3Bg2 commented on GitHub (May 8, 2025): @rajkumar-cp Have you been able to check the exported json? Is it unstructured? Cannot replicate it on my end.

kerem commented

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

Author

Owner

@Gabrielgps25 commented on GitHub (May 29, 2025):

Here we are working in a team with 10 people collaborating into collection and we have some folders with regression tests. Every time that I open Hoppscotch at browser the requests are unordered. Seams that it's more frequently when two or more people are using Hoppscotch Workspace at the same time. We're not exporting collections, only creating, editing and saving collections under Workspace.

Exemple:
Using Browser, I opened 1 regression test folder and found this order:

Manually I've adjusted requests order:

After refreshing page w/o cache (Ctrl + Shift + R), found this order:

@Gabrielgps25 commented on GitHub (May 29, 2025): Here we are working in a team with 10 people collaborating into collection and we have some folders with regression tests. Every time that I open Hoppscotch at browser the requests are unordered. Seams that it's more frequently when two or more people are using Hoppscotch Workspace at the same time. We're not exporting collections, only creating, editing and saving collections under Workspace. Exemple: Using Browser, I opened 1 regression test folder and found this order: ![Image](https://github.com/user-attachments/assets/9d80cb3f-3725-4f24-bdff-4c3ca2d2db7a) Manually I've adjusted requests order: ![Image](https://github.com/user-attachments/assets/574b6d5c-8692-4203-b0ca-bf5d8c5f20b1) After refreshing page w/o cache (Ctrl + Shift + R), found this order: ![Image](https://github.com/user-attachments/assets/19da2792-ec2f-4266-9182-1d3efa2fdbd2)

kerem commented

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

Author

Owner

@yafimchik commented on GitHub (Jun 5, 2025):

I confirm the existence of this bug. Our team is just getting familiar with this tool and have already encountered this issue. The order of requests in a collection is critically important to us, but the order in which requests are displayed in the interface does not match the order when exporting or running the entire collection.

We noticed that after refreshing the page, the current test run order is displayed in the interface. We can see that this order is indeed incorrect, but when trying to change the order, unexpected behavior occurs — either a request moves to the wrong position, or a different request’s order changes instead. Refreshing the page does not fix this bug; it only provides a chance to see the actual request order in the interface.

Seems that it's a frontend bug.

UPD: looks like reordering of the collection fails more frequiently if you've already run this collection.

@yafimchik commented on GitHub (Jun 5, 2025): I confirm the existence of this bug. Our team is just getting familiar with this tool and have already encountered this issue. The order of requests in a collection is critically important to us, but the order in which requests are displayed in the interface does not match the order when exporting or running the entire collection. We noticed that after refreshing the page, the current test run order is displayed in the interface. We can see that this order is indeed incorrect, but when trying to change the order, unexpected behavior occurs — either a request moves to the wrong position, or a different request’s order changes instead. Refreshing the page does not fix this bug; it only provides a chance to see the actual request order in the interface. Seems that it's a frontend bug. UPD: looks like reordering of the collection fails more frequiently if you've already run this collection.

kerem commented

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

Author

Owner

@gbespyatykh commented on GitHub (Jun 5, 2025):

I confirm this behavior. Correct requests order is critical requirement for some multistep scenarios, but it seems not working

This could be a fast workaround: https://github.com/hoppscotch/hoppscotch/pull/4785

Please pay attention to the problem

@gbespyatykh commented on GitHub (Jun 5, 2025): I confirm this behavior. Correct requests order is critical requirement for some multistep scenarios, but it seems not working This could be a fast workaround: https://github.com/hoppscotch/hoppscotch/pull/4785 Please pay attention to the problem

kerem referenced this issue

2026-03-17 01:09:12 +03:00

[PR #1889] [MERGED] chore: add json file extension #3546