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 is not helping the user fix errors on saved objects for deprecated scripted field doc['timestamp'].value.hourOfDay #122365

Closed
Tracked by #170754
bhavyarm opened this issue Jan 5, 2022 · 8 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Dashboard Dashboard related features Icebox 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 Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.

Comments

@bhavyarm
Copy link
Contributor

bhavyarm commented Jan 5, 2022

Kibana version: 8.0.0 rc1

Elasticsearch version: 8.0.0 rc1

Server OS version: darwin_x86_64

Browser version: chrome latest

Browser OS version: OS X

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

Describe the bug: Currently Kibana just displays error on saved search panel if search has fields with scripted field defined with doc['timestamp'].value.hourOfDay.

Screen Shot 2022-01-05 at 12 27 00 PM

The error shows up only in discover after user clicks edit and navigates to discover -
Screen Shot 2022-01-05 at 12 30 19 PM

Can we please add some details in the dashboard panel for the error?

I am seeing this on flights sample dashboard upgraded from 6.8 to 8.0.0 in my local.

@bhavyarm bhavyarm added bug Fixes for quality problems that affect the customer experience Feature:Dashboard Dashboard related features Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas labels Jan 5, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-presentation (Team:Presentation)

@kibanamachine kibanamachine added impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:needs-research This issue requires some research before it can be worked on or estimated labels Jan 5, 2022
@ThomThomson
Copy link
Contributor

I think this needs to be updated on the Discover side, I have changed the tags.

@ThomThomson ThomThomson added Feature:Discover Discover Application Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL. and removed Feature:Dashboard Dashboard related features Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas labels Jan 5, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

@kertal kertal added the loe:small Small Level of Effort label Jan 10, 2022
@kertal
Copy link
Member

kertal commented Jan 10, 2022

yes, we should improve this!

@kertal kertal removed loe:needs-research This issue requires some research before it can be worked on or estimated impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Jan 10, 2022
@bhavyarm
Copy link
Contributor Author

This also happens on heatmap viz. Plus when you click on edit script - Kibana just plunks the user on index pattern management page. Not the specific scripted field user needs to fix.

Here is the error on viz on dashboard:
Screen Shot 2022-01-11 at 11 22 14 AM

on the viz
Screen Shot 2022-01-11 at 11 22 27 AM

When user clicks on edit script:

edit_script.mp4

I think this bug belongs to appservices?

@bhavyarm bhavyarm changed the title Kibana just displays error and no other details on saved search panel with search saved with deprecated scripted field doc['timestamp'].value.hourOfDay Kibana is not helping the user fix errors on saved objects for deprecated scripted field doc['timestamp'].value.hourOfDay Jan 11, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app-services (Team:AppServicesUx)

@exalate-issue-sync exalate-issue-sync bot added the impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. label Feb 1, 2022
@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. and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. labels Mar 18, 2022
@kertal
Copy link
Member

kertal commented Jul 29, 2022

I've checked for Discover, Saved searches, in the meantime it doesn't pretend there are no results, so the bug showing the wrong screen was solved in the meantime.
Bildschirmfoto 2022-07-29 um 16 25 25
however EsError: runtime error is not very helpful, but that's the error we get in this case, so this for sure can't be improved. but I guess it's @elastic/kibana-app-services territory, error reporting on a dashboard? relabeling the issue a bit

@kertal kertal added Feature:Dashboard Dashboard related features and removed Feature:Discover Discover Application :DataDiscovery/fix-it-week labels Jul 29, 2022
@kertal kertal added the Icebox label Nov 27, 2023
@kertal
Copy link
Member

kertal commented Nov 27, 2023

Closing this because it's not planned to be resolved in the foreseeable future. It will be tracked in our Icebox and will be re-opened if our priorities change. Feel free to re-open if you think it should be melted sooner.

@kertal kertal closed this as not planned Won't fix, can't repro, duplicate, stale Nov 27, 2023
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:Dashboard Dashboard related features Icebox 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 Team:DataDiscovery Discover, search (e.g. data plugin and KQL), data views, saved searches. For ES|QL, use Team:ES|QL.
Projects
None yet
Development

No branches or pull requests

5 participants