starred/hoppscotch

Fork 0

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

[GH-ISSUE #4933] [bug]: Collections Pagination Issue - Not All Collections Are Visible #1861

New issue

Closed

opened 2026-03-16 22:08:58 +03:00 by kerem · 8 comments

kerem commented

2026-03-16 22:08:58 +03:00

Owner

Originally created by @Elghazal on GitHub (Mar 24, 2025).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4933

Originally assigned to: @nivedin on GitHub.

Is there an existing issue for this?

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

Current behavior

We recently migrated from Postman to Hoppscotch (self-hosted), and we are extremely happy with the experience! أoppscotch is lightweight, fast, and meets most of our needs. However, we encountered an issue where not all collections appear in the sidebar. It seems there is a problem related to pagination or loading a large number of collections.

To work around this, we created a new collection named "archive" and moved less frequently used collections into it. This allowed us to see previously invisible collections. However, this is not an ideal solution, and we'd appreciate a fix for proper collection pagination or loading.

Expected Behavior:
All collections should be visible in the sidebar, or there should be a clear pagination mechanism to access them.

Steps to reproduce

Add a large number of collections in Hoppscotch.

Check the sidebar and note that some collections are missing.

Moving some collections to a new collection (e.g., "archive") reveals previously hidden ones.

Logs and Screenshots

Environment

Production

Hoppscotch Version

Self-hosted

Interceptor

Not Applicable - Issue not related to network requests

Browsers Affected

Chrome

Operating System

MacOS

Additional Information

No response

Originally created by @Elghazal on GitHub (Mar 24, 2025). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4933 Originally assigned to: @nivedin on GitHub. ### Is there an existing issue for this? - [x] I have searched existing issues and this bug hasn't been reported yet ### Current behavior We recently migrated from Postman to Hoppscotch (self-hosted), and we are extremely happy with the experience! أoppscotch is lightweight, fast, and meets most of our needs. However, we encountered an issue where not all collections appear in the sidebar. It seems there is a problem related to pagination or loading a large number of collections. To work around this, we created a new collection named "**archive**" and moved less frequently used collections into it. This allowed us to see previously invisible collections. However, this is not an ideal solution, and we'd appreciate a fix for proper collection pagination or loading. Expected Behavior: All collections should be visible in the sidebar, or there should be a clear pagination mechanism to access them. ### Steps to reproduce Add a large number of collections in Hoppscotch. Check the sidebar and note that some collections are missing. Moving some collections to a new collection (e.g., "archive") reveals previously hidden ones. ### Logs and Screenshots ```shell ``` ### Environment Production ### Hoppscotch Version Self-hosted ### Interceptor Not Applicable - Issue not related to network requests ### Browsers Affected Chrome ### Operating System MacOS ### Additional Information _No response_

kerem

2026-03-16 22:08:58 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-16 22:09:14 +03:00

Author

Owner

@nivedin commented on GitHub (Mar 25, 2025):

@Elghazal thank you for reporting the issue. Are you missing collections from the initial root collection list or child folders inside a collection?
Just to confirm this issue is happening inside a team workspace right ?

@nivedin commented on GitHub (Mar 25, 2025): @Elghazal thank you for reporting the issue. Are you missing collections from the initial root collection list or child folders inside a collection? Just to confirm this issue is happening inside a team workspace right ?

kerem commented

2026-03-16 22:09:19 +03:00

Author

Owner

@Elghazal commented on GitHub (Mar 25, 2025):

Exactly, the issue occurs in the initial root collection list within our team workspace.

@Elghazal commented on GitHub (Mar 25, 2025): Exactly, the issue occurs in the initial root collection list within our team workspace.

kerem commented

2026-03-16 22:09:24 +03:00

Author

Owner

@nivedin commented on GitHub (Mar 25, 2025):

@Elghazal we were not able to reproduce the issue. Is this issue happening for other users in the workspace ?

@nivedin commented on GitHub (Mar 25, 2025): @Elghazal we were not able to reproduce the issue. Is this issue happening for other users in the workspace ?

kerem commented

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

Author

Owner

@Elghazal commented on GitHub (Mar 25, 2025):

It's happening to all team members in the workspace.

We have 48 collections, and we were forced to move 18 of them into a sub-collection (archive collection) as a workaround. This allowed the remaining 30 collections to be displayed in the root.

When I tried to reproduce the issue, I noticed that I cannot move a sub-collection back to the initial root collection. Instead, it can only be moved to another sub-collection!

@Elghazal commented on GitHub (Mar 25, 2025): It's happening to all team members in the workspace. We have 48 collections, and we were forced to move 18 of them into a sub-collection (archive collection) as a workaround. This allowed the remaining 30 collections to be displayed in the root. When I tried to reproduce the issue, I noticed that I cannot move a sub-collection back to the initial root collection. Instead, it can only be moved to another sub-collection!

kerem commented

2026-03-16 22:09:35 +03:00

Author

Owner

@nivedin commented on GitHub (Mar 26, 2025):

@Elghazal Thank you for the detailed information. Let us check this and get back to you, also can you let me know the app version you are using.

@nivedin commented on GitHub (Mar 26, 2025): @Elghazal Thank you for the detailed information. Let us check this and get back to you, also can you let me know the app version you are using.

kerem commented

2026-03-16 22:09:40 +03:00

Author

Owner

@Elghazal commented on GitHub (Mar 26, 2025):

@nivedin
Thank you! The Hoppscotch version we are using is "V2025.2.2" Let me know if you need any further details.

@Elghazal commented on GitHub (Mar 26, 2025): @nivedin Thank you! The Hoppscotch version we are using is "V2025.2.2" Let me know if you need any further details.

kerem commented

2026-03-16 22:09:45 +03:00

Author

Owner

@alaaelbarasi commented on GitHub (Apr 13, 2025):

I'm facing the same issue, using Hoppscotch version 2025.3.0

@alaaelbarasi commented on GitHub (Apr 13, 2025): I'm facing the same issue, using Hoppscotch version 2025.3.0

kerem commented

2026-03-16 22:09:50 +03:00

Author

Owner

@mirarifhasan commented on GitHub (Aug 29, 2025):

Hi everyone,

We’ve addressed this issue in our latest release v2025.8.0. Could you please try updating to the latest version and let us know if you’re still experiencing the problem?

@mirarifhasan commented on GitHub (Aug 29, 2025): Hi everyone, We’ve addressed this issue in our latest release **v2025.8.0**. Could you please try updating to the latest version and let us know if you’re still experiencing the problem?