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

[SR] Policy wizard steps are not disabled when form is invalid #58773

Closed
alisonelizabeth opened this issue Feb 27, 2020 · 2 comments · Fixed by #76540
Closed

[SR] Policy wizard steps are not disabled when form is invalid #58773

alisonelizabeth opened this issue Feb 27, 2020 · 2 comments · Fixed by #76540
Labels
bug Fixes for quality problems that affect the customer experience Feature:Snapshot and Restore Elasticsearch snapshots and repositories UI good first issue low hanging fruit Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more

Comments

@alisonelizabeth
Copy link
Contributor

Steps to reproduce:

  1. Navigate to the Polices tab in Snapshot & Restore and create a policy.

  2. Proceed to step 2 (Snapshot settings).

  3. Select an index from the list of indices, then deselect it. A field error should display and the "Next" button should be disabled. Note step 1 (Logistics) is still enabled.

Screen Shot 2020-02-27 at 3 31 01 PM

  1. Navigate back to step 1 (Logistics).

  2. Note the Next button is still disabled and the user is stuck unless the browser is refreshed.

Screen Shot 2020-02-27 at 3 31 09 PM

Expected behavior:
I would expect the previous steps to also be disabled if there is a field error.

@alisonelizabeth alisonelizabeth added bug Fixes for quality problems that affect the customer experience Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more Feature:Snapshot and Restore Elasticsearch snapshots and repositories UI labels Feb 27, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/es-ui (Team:Elasticsearch UI)

@alisonelizabeth
Copy link
Contributor Author

This also occurs if you have an invalid field on the retention step (e.g., min count greater than max count) and go back to a previous step without fixing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Snapshot and Restore Elasticsearch snapshots and repositories UI good first issue low hanging fruit Team:Kibana Management Dev Tools, Index Management, Upgrade Assistant, ILM, Ingest Node Pipelines, and more
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants