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

Kibana Spaces - Loss of data when editing a Space #42503

Open
barlowm opened this issue Aug 2, 2019 · 2 comments
Open

Kibana Spaces - Loss of data when editing a Space #42503

barlowm opened this issue Aug 2, 2019 · 2 comments
Labels
enhancement New value added to drive a business result Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! usability

Comments

@barlowm
Copy link
Collaborator

barlowm commented Aug 2, 2019

Kibana version:
7.3

Elasticsearch version:

Server OS version:

Browser version:

Browser OS version:

Original install method (e.g. download page, yum, from source, etc.):

Describe the bug:
Create a new or edit existing space within the "Manage Spaces"
Click the "roles"

Steps to reproduce:

  1. Navigate to the "Manage Spaces" button and click it.
  2. The "Spaces" page opens.
  3. Click the "Create a space" button
  4. Select the "Name" field and enter a name (or modify an existing name)
  5. Click the "Roles" link at the bottom of the page
    Spaces2
  6. Notification of "Security Disabled"
    Spaces3
  7. Go back to the spaces page that was being edited.
  8. Edits are lost

Expected behavior:
User should be prompted to save data before being allowed to go to the "Roles" page

Screenshots (if relevant):

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

@barlowm barlowm added the bug Fixes for quality problems that affect the customer experience label Aug 2, 2019
@myasonik myasonik added enhancement New value added to drive a business result usability labels Aug 2, 2019
@myasonik
Copy link
Contributor

myasonik commented Aug 2, 2019

Probably all forms across Kibana should either:

  1. notify the user that they're about to lose data
  2. save a draft state of the form so it's pre-filled in for next time (but then that probably requires more design for trashing the draft completely)

@lukeelmers lukeelmers added the Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! label Aug 2, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security

@kobelb kobelb removed the bug Fixes for quality problems that affect the customer experience label Jan 14, 2020
@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Aug 5, 2021
@legrego legrego removed EnableJiraSync loe:small Small Level of Effort impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. labels Aug 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! usability
Projects
None yet
Development

No branches or pull requests

6 participants