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

Back button on Configure Resources does not keep entered information #6086

Closed
3 of 8 tasks
Dewain27 opened this issue Mar 2, 2021 · 0 comments · Fixed by #6309
Closed
3 of 8 tasks

Back button on Configure Resources does not keep entered information #6086

Dewain27 opened this issue Mar 2, 2021 · 0 comments · Fixed by #6309
Assignees
Labels
Milestone

Comments

@Dewain27
Copy link
Contributor

Dewain27 commented Mar 2, 2021

Describe the bug

When creating a publishing profile, when on the Configure Resource page of the publishing profile and you hit the back button it does not retain the information you entered on the prior screen.

Version

image

Browser

  • Electron distribution
  • Chrome
  • Safari
  • Firefox
  • Edge

OS

  • macOS
  • Windows
  • Ubuntu

To Reproduce

Steps to reproduce the behavior:

  1. Go to create a publishing profile
  2. Add Name and Publishing target
  3. Click Next: Configure resources
  4. Click Back
  5. All data is gone that was entered before

Expected behavior

Information provided should have persisted to allow me to change without re-entering all data.

Screenshots

image

Additional context

@Dewain27 Dewain27 added Type: Bug Something isn't working Needs-triage A new issue that require triage R12 Bugbash labels Mar 2, 2021
@benbrown benbrown added this to the R12 milestone Mar 4, 2021
@cwhitten cwhitten added P0 Must Fix. Release-blocker and removed Needs-triage A new issue that require triage labels Mar 4, 2021
@benbrown benbrown modified the milestones: R12, R13 Mar 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants