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

Saved Object editor doesn't allow for edits #129096

Closed
TheRiffRafi opened this issue Mar 31, 2022 · 7 comments
Closed

Saved Object editor doesn't allow for edits #129096

TheRiffRafi opened this issue Mar 31, 2022 · 7 comments
Labels
bug Fixes for quality problems that affect the customer experience Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@TheRiffRafi
Copy link

TheRiffRafi commented Mar 31, 2022

Kibana version: 8.1.1

Elasticsearch version: 8.1.1

Describe the bug: The Kibana documentation states that one can edit certain saved objects.
However no saved object can be edited, we receive a message of type "Cannot edit in read-only editor" and there is no place to switch a write editor.

Steps to reproduce:

  1. Create visualization in Kibana.
  2. Go to "Stack Management - Kibana - Saved Objects"
  3. Inspect the created visualization and attempt to edit values.

Expected behavior:
Either data should be editable or there should be an option to switch to a writable editor.

Screenshots (if relevant):
Screen Shot 2022-03-31 at 11 10 35

Any additional context:
This was possible in version 7.x and there doesn't seem to be any docs stating that it isn't supposed to work now.

Work arounds:
Currently we have 2 work arounds.
We can either export the object, modify it in text, delete the original object, and import it with the changes.
Or, we can use the saved object api instead to modify the object:
https://www.elastic.co/guide/en/kibana/8.1/saved-objects-api-update.html

@TheRiffRafi TheRiffRafi added the bug Fixes for quality problems that affect the customer experience label Mar 31, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Mar 31, 2022
@LeeDr LeeDr added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Apr 1, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@botelastic botelastic bot removed the needs-team Issues missing a team label label Apr 1, 2022
@LeeDr
Copy link

LeeDr commented Apr 1, 2022

It seems this was an intentional change. The change was made in 8.0 here #112034
I filed a docs issue on it here #129252

@LeeDr
Copy link

LeeDr commented Apr 1, 2022

I'm going to close this since it was an intentional change and there's an open issue to update the docs.

There are work-arounds as mentioned in the description above.

@ndunks
Copy link

ndunks commented Nov 7, 2022

So, is there a way to change referenced index? Kibana saved discover break when I recreate Data View index, any solution of this instead of recreating it? at least I can copy the defined columns

@TinaHeiligers
Copy link
Contributor

@ndunks you'll have to use the UI to create a new saved search in Discover.
You could try the export/import option and see if that helps.

@LeeDr
Copy link

LeeDr commented Nov 8, 2022

@ndunks Also, this might not be obvious, but when you create a new index pattern you can set the id of it (in the advanced settings).

So if you export your saved search and find the referenced index pattern you can re-create that index pattern and use the advanced settings to set it to that id. This would be for a case where you accidentally deleted the index pattern.

@ndunks
Copy link

ndunks commented Nov 8, 2022

okay thanks, will try if I face it again.

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 Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

5 participants