[GH-ISSUE #5956] [feature]: Reveal current request in collection sidebar #2339

New issue

Open

opened 2026-03-17 00:00:48 +03:00 by kerem · 3 comments

kerem commented

2026-03-17 00:00:48 +03:00

Owner

Originally created by @MikolajPiecekMoliera on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5956

Is there an existing issue for this?

I have searched the existing issues

Summary

Add an action to reveal the currently open request in the collection sidebar. When triggered, the application should expand the relevant collection and folder hierarchy and highlight the request that is currently open in the editor. This would allow users to quickly locate the request within the collection structure without manually searching or scrolling through large collections.

Why should this be worked on?

When working with large collections, it can be difficult to find the position of the currently open request in the sidebar. Requests are often opened via search, duplication, imports, or navigation between tabs, which makes it easy to lose context within the collection hierarchy. A “Reveal in collection” action would quickly restore this context by expanding and highlighting the request’s location. This improves navigation, helps users understand the organization of their collections, and aligns the workflow with similar functionality available in tools like Postman, Insomnia, and many IDE file explorers.

Originally created by @MikolajPiecekMoliera on GitHub (Mar 6, 2026). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5956 ### Is there an existing issue for this? - [x] I have searched the existing issues ### Summary Add an action to reveal the currently open request in the collection sidebar. When triggered, the application should expand the relevant collection and folder hierarchy and highlight the request that is currently open in the editor. This would allow users to quickly locate the request within the collection structure without manually searching or scrolling through large collections. ### Why should this be worked on? When working with large collections, it can be difficult to find the position of the currently open request in the sidebar. Requests are often opened via search, duplication, imports, or navigation between tabs, which makes it easy to lose context within the collection hierarchy. A “Reveal in collection” action would quickly restore this context by expanding and highlighting the request’s location. This improves navigation, helps users understand the organization of their collections, and aligns the workflow with similar functionality available in tools like Postman, Insomnia, and many IDE file explorers.

kerem added the

feature

label

2026-03-17 00:00:48 +03:00

kerem commented

2026-03-17 00:00:59 +03:00

Author

Owner

@statxc commented on GitHub (Mar 6, 2026):

@jamesgeorge007 Can I take on this? I'd like to contribute

@statxc commented on GitHub (Mar 6, 2026): @jamesgeorge007 Can I take on this? I'd like to contribute

kerem commented

2026-03-17 00:01:04 +03:00

Author

Owner

@PrathamPeriwal commented on GitHub (Mar 11, 2026):

Hi! I’m interested in contributing and would like to work on this issue. Please let me know if I can be assigned.

@PrathamPeriwal commented on GitHub (Mar 11, 2026): Hi! I’m interested in contributing and would like to work on this issue. Please let me know if I can be assigned.

kerem commented

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

Author

Owner

@saksham242007 commented on GitHub (Mar 13, 2026):

Hi! I’d like to work on this feature. My plan is to track the currently open request’s ID and then expand the corresponding collection and folder hierarchy in the sidebar, highlighting the request. Would love to hear any feedback on this approach before I start.

@saksham242007 commented on GitHub (Mar 13, 2026): Hi! I’d like to work on this feature. My plan is to track the currently open request’s ID and then expand the corresponding collection and folder hierarchy in the sidebar, highlighting the request. Would love to hear any feedback on this approach before I start.

kerem referenced this issue

2026-03-17 01:19:52 +03:00

[PR #2339] [CLOSED] chore(deps): bump husky from 7.0.4 to 8.0.1 #3745