[GH-ISSUE #3243] [bug]: Saving already saved GraphQL request opens up "Save As" dialogue instead of just saving it to its original name #1077

New issue

Open

opened 2026-03-16 18:24:52 +03:00 by kerem · 2 comments

kerem commented

2026-03-16 18:24:52 +03:00

Owner

Originally created by @incrypto32 on GitHub (Aug 6, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3243

Is there an existing issue for this?

I have searched the existing issues

Current behavior

When i save a already saved GraphQL request after making some changes, it opens up the "Save As" dialogue instead of just saving it

Steps to reproduce

Save a GraphQL request to a collection
Make some changes to it
Hit Ctrl + S
This opens up the Save As dialouge instead of just saving the changes to the current file

Environment

Production

Version

Cloud

Originally created by @incrypto32 on GitHub (Aug 6, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3243 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior When i save a already saved GraphQL request after making some changes, it opens up the "Save As" dialogue instead of just saving it ### Steps to reproduce 1. Save a GraphQL request to a collection 2. Make some changes to it 3. Hit Ctrl + S 4. This opens up the Save As dialouge instead of just saving the changes to the current file ### Environment Production ### Version Cloud

kerem added the

bug

need testing

labels

2026-03-16 18:24:52 +03:00

kerem commented

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

Author

Owner

@Bharat-kr commented on GitHub (Oct 28, 2023):

I can Solve this bug should i start on it or wait for it to get assigned ?

@Bharat-kr commented on GitHub (Oct 28, 2023): I can Solve this bug should i start on it or wait for it to get assigned ?

kerem commented

2026-03-16 18:25:08 +03:00

Author

Owner

@liyasthomas commented on GitHub (Oct 29, 2023):

Hi @incrypto32, I couldn't reproduce this issue at my end.

@liyasthomas commented on GitHub (Oct 29, 2023): Hi @incrypto32, I couldn't reproduce this issue at my end.

kerem referenced this issue

2026-03-17 00:41:40 +03:00

[PR #1077] [MERGED] Issue/1076 #3044