Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating a form by opening a form file does not save it to account when signed in #3628

Open
anikbrazeau opened this issue May 14, 2024 · 3 comments
Labels
bug Something isn't working 🚦 Severe Severe Impact Issue

Comments

@anikbrazeau
Copy link
Member

anikbrazeau commented May 14, 2024

Description

When importing a JSON form file to create a form, it opens in the Preview/Test section. If you go to Forms, that form does not save to your forms. It seems you need to take the extra step to go to Edit and actually name the file and click save? This could lead to confusion and losing forms when importing more than one in succession.

Steps to reproduce

  1. Go to GC Forms
  2. Open a form file
  3. Go to Forms
  4. Go to Create new form
  5. Open another form file
  6. Go to Forms
  7. Notice it's empty

Details

  • Browser: Edge
  • Operating system: Windows
  • Environment: Staging
  • Language: French
  • Viewport: Desktop

Expected behaviour

Auto-named and auto-saved when imported?

Screenshots or videos

Opens to preview but does not save

@anikbrazeau anikbrazeau added the bug Something isn't working label May 14, 2024
@anikbrazeau anikbrazeau changed the title Opening a file does not save it to account when signed in Creating a form by opening a form file does not save it to account when signed in May 14, 2024
@timarney
Copy link
Member

Been wondering for a while if we should be taking folks to edit vs preview first ... thoughts?

@anikbrazeau
Copy link
Member Author

Yeah I think that might be more expected? Or I wonder if conserving the name of the file and saving it when uploaded might also help if they land on preview?

@Abi-Nada
Copy link

Hi folks! This behaviour currently persists in Production - I'm going to de-scope it from the App Router work, and we can prioritize outside of this work

@srtalbot srtalbot added the 🚦 Severe Severe Impact Issue label May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working 🚦 Severe Severe Impact Issue
Projects
None yet
Development

No branches or pull requests

4 participants