[GH-ISSUE #3938] [bug]: experimental feature "expand navigation" doesn't work #1377

Open
opened 2026-03-16 20:04:30 +03:00 by kerem · 5 comments
Owner

Originally created by @ANSI-C on GitHub (Mar 27, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3938

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

when I open an API via link url the sidebar doesn't get automatically expanded to the API call I land on.

Steps to reproduce

  1. go to an api
  2. click "share request" then select "link", then "create", then "copy link" (this procedure is rather long and clumsy BTW)
  3. close the browser tab and paste the link on a new tab
  4. I should land on the previous call with the treeview on the sidebar expanded to the same call

Environment

Production

Version

Cloud

Originally created by @ANSI-C on GitHub (Mar 27, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3938 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior when I open an API via link url the sidebar doesn't get automatically expanded to the API call I land on. ### Steps to reproduce 1. go to an api 2. click "share request" then select "link", then "create", then "copy link" (this procedure is rather long and clumsy BTW) 3. close the browser tab and paste the link on a new tab 4. I should land on the previous call **with the treeview on the sidebar expanded to the same call** ### Environment Production ### Version Cloud
Author
Owner

@joeljstephen commented on GitHub (Apr 9, 2024):

Hi @ANSI-C. Sharing a request does not provide others with access to your request or collections. Instead, it generates a link that references your request, and this link can be shared with anyone and they can generate a copy of your request. Could you help us understand what use case you were trying to achieve so that we can understand this better?

<!-- gh-comment-id:2045179253 --> @joeljstephen commented on GitHub (Apr 9, 2024): Hi @ANSI-C. Sharing a request does not provide others with access to your request or collections. Instead, it generates a link that references your request, and this link can be shared with anyone and they can generate a copy of your request. Could you help us understand what use case you were trying to achieve so that we can understand this better?
Author
Owner

@ANSI-C commented on GitHub (Apr 9, 2024):

Yes, we would like a mean to share same requests in a teamwork to be able to use/update them with a fixed link, possibly shown in the browser url, maybe pointed by url fragment, if not available otherwise.

<!-- gh-comment-id:2045235450 --> @ANSI-C commented on GitHub (Apr 9, 2024): Yes, we would like a mean to share same requests in a teamwork to be able to use/update them with a fixed link, possibly shown in the browser url, maybe pointed by url fragment, if not available otherwise.
Author
Owner

@thetronjohnson commented on GitHub (Apr 9, 2024):

@ANSI-C is there a reason why creating a new workspace and inviting your team to the workspace won't work for you? Workspace are generally the goto option for collaboration

<!-- gh-comment-id:2045265766 --> @thetronjohnson commented on GitHub (Apr 9, 2024): @ANSI-C is there a reason why creating a new workspace and inviting your team to the workspace won't work for you? Workspace are generally the goto option for collaboration
Author
Owner

@ANSI-C commented on GitHub (Apr 9, 2024):

what if I want to document the call in an internal ticketing or KB system?

<!-- gh-comment-id:2045382366 --> @ANSI-C commented on GitHub (Apr 9, 2024): what if I want to document the call in an internal ticketing or KB system?
Author
Owner

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

@thetronjohnson, this would be a valuable feature for the workspace maybe? a unique link for each request that can be easily shared to that team member.

<!-- gh-comment-id:2699291849 --> @anwarulislam commented on GitHub (Mar 4, 2025): @thetronjohnson, this would be a valuable feature for the workspace maybe? a unique link for each request that can be easily shared to that team member.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#1377
No description provided.