-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Editing a scripted field causes errors #33251
Labels
bug
Fixes for quality problems that affect the customer experience
Feature:Kibana Management
Feature label for Data Views, Advanced Setting, Saved Object management pages
Comments
lukasolson
added
bug
Fixes for quality problems that affect the customer experience
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
Feature:Kibana Management
Feature label for Data Views, Advanced Setting, Saved Object management pages
labels
Mar 14, 2019
Pinging @elastic/kibana-app |
Ironically, refreshing the page seems to fix the error. |
lukeelmers
added
:AppArch
and removed
Team:Visualizations
Visualization editors, elastic-charts and infrastructure
labels
Mar 27, 2019
3 tasks
lizozom
pushed a commit
to lizozom/kibana
that referenced
this issue
Apr 8, 2019
fixed by #34679 |
lizozom
added a commit
that referenced
this issue
Apr 11, 2019
lizozom
added a commit
to lizozom/kibana
that referenced
this issue
Apr 11, 2019
* Changed the default fieldFormatMap to undefined - bugfix * Test for bug elastic#33251 * Remove only
1 task
42 tasks
This was referenced Jan 26, 2021
2 tasks
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:Kibana Management
Feature label for Data Views, Advanced Setting, Saved Object management pages
Steps to reproduce:
You'll get a blank page and the following error in the console:
If you try to go to Discover with that index pattern selected, you'll get this error:
Looks like the field formatter is not being saved the second time around, not sure exactly why.
The text was updated successfully, but these errors were encountered: