starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-25 16:55:59 +03:00

[GH-ISSUE #4383] [bug]: GraphQL collections are not shared in a workspace #1601

New issue

Open

opened 2026-03-16 21:02:12 +03:00 by kerem · 7 comments

kerem commented

2026-03-16 21:02:12 +03:00

Owner

Originally created by @tvvignesh on GitHub (Sep 29, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4383

Is there an existing issue for this?

I have searched the existing issues

Current behavior

We created a workspace, added team members and provided them editor and admin access in hoppscotch. The issue is that while REST APIs we create are visible across members in the team, GraphQL APIs are not (irrespective of who created it)

We are unable to use hoppscotch to collaborate with GraphQL because of this. Kindly help.

Steps to reproduce

Create a workspace and add team members into it
Create a collection, save GQL requests into the collection as team member 1
Team member 2 tries to see the collection and he/she sees nothing in GQL but sees collections in REST

Environment

Production

Version

Self-hosted

Originally created by @tvvignesh on GitHub (Sep 29, 2024). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4383 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior We created a workspace, added team members and provided them editor and admin access in hoppscotch. The issue is that while REST APIs we create are visible across members in the team, GraphQL APIs are not (irrespective of who created it) We are unable to use hoppscotch to collaborate with GraphQL because of this. Kindly help. ### Steps to reproduce 1. Create a workspace and add team members into it 1. Create a collection, save GQL requests into the collection as team member 1 2. Team member 2 tries to see the collection and he/she sees nothing in GQL but sees collections in REST ### Environment Production ### Version Self-hosted

kerem added the

bug

need testing

labels

2026-03-16 21:02:12 +03:00

kerem commented

2026-03-16 21:02:23 +03:00

Author

Owner

@MVelez94 commented on GitHub (Sep 30, 2024):

Hey, I'd like to work on this one.

@MVelez94 commented on GitHub (Sep 30, 2024): Hey, I'd like to work on this one.

kerem commented

2026-03-16 21:02:28 +03:00

Author

Owner

@tvvignesh commented on GitHub (Nov 16, 2024):

@jamesgeorge007 @AndrewBastin @CuriousCorrelation Tagging you all for visibility. Thanks a lot.

Another issue is lack of environment support in GraphQL which is being tracked here: https://github.com/hoppscotch/hoppscotch/issues/2172

If both are done, hoppscotch would be complete for us. We are using it comprehensively and would love to give feedback and help in the process. Thanks in advance.

@tvvignesh commented on GitHub (Nov 16, 2024): @jamesgeorge007 @AndrewBastin @CuriousCorrelation Tagging you all for visibility. Thanks a lot. Another issue is lack of environment support in GraphQL which is being tracked here: https://github.com/hoppscotch/hoppscotch/issues/2172 If both are done, hoppscotch would be complete for us. We are using it comprehensively and would love to give feedback and help in the process. Thanks in advance.

kerem commented

2026-03-16 21:02:33 +03:00

Author

Owner

@toddgower-hiatus commented on GitHub (Feb 28, 2025):

Unfortunately, this issue prevents us from using Hoppscotch. Is there any movement towards getting this working? Seems like it's not that much of a stretch to share GQL collections since it already works for REST/

@toddgower-hiatus commented on GitHub (Feb 28, 2025): Unfortunately, this issue prevents us from using Hoppscotch. Is there any movement towards getting this working? Seems like it's not that much of a stretch to share GQL collections since it already works for REST/

kerem commented

2026-03-16 21:02:38 +03:00

Author

Owner

@ivank commented on GitHub (Mar 20, 2025):

This is affecting us as well! Neither Environment variables nor the collections for themselves for graphql are stored in the workspace.

@ivank commented on GitHub (Mar 20, 2025): This is affecting us as well! Neither Environment variables nor the collections for themselves for graphql are stored in the workspace.

kerem commented

2026-03-16 21:02:43 +03:00

Author

Owner

@sanirasheed commented on GitHub (Jun 3, 2025):

was this resloved?

@sanirasheed commented on GitHub (Jun 3, 2025): was this resloved?

kerem commented

2026-03-16 21:02:48 +03:00

Author

Owner

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

We would like to have this too. Can we expect this feature to be implemented in the near future?

@ThiloHettmer commented on GitHub (Jun 5, 2025): We would like to have this too. Can we expect this feature to be implemented in the near future?

kerem commented

2026-03-16 21:02:53 +03:00

Author

Owner

@EverWinter23 commented on GitHub (Dec 18, 2025):

We are also facing the same issue.

@EverWinter23 commented on GitHub (Dec 18, 2025): We are also facing the same issue.