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.

Sign up for GitHub

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

Jump to bottom

Reporting should display clearer error message if dashboard has saved object not found panel #97904

Closed
bhavyarm opened this issue Apr 21, 2021 · 4 comments
Closed

Reporting should display clearer error message if dashboard has saved object not found panel #97904

bhavyarm opened this issue Apr 21, 2021 · 4 comments
Labels
bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:medium Medium Level of Effort

Comments

@bhavyarm
Copy link
Contributor

Kibana version: 7.12.1

Elasticsearch version: 7.12.1

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: If user tries to print a report on a dashboard where one of the panels has saved object not found error - reporting fails. And you can see error: object on reporting table. We can make this clear to tell the user to go and check their object or add saved object id which is causing all the trouble.

Found while testing this -
#97880

Screen Shot 2021-04-21 at 4 23 59 PM
@bhavyarm bhavyarm added bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Team:AppServices labels Apr 21, 2021
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

@tsullivan tsullivan added Team:Visualizations Visualization editors, elastic-charts and infrastructure and removed Team:AppServices labels May 5, 2021
@timroes timroes added Team:AppServices and removed Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Jul 22, 2021
@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 Jul 22, 2021
@tsullivan tsullivan mentioned this issue Jul 27, 2021
Closed
@tsullivan
Copy link
Member

Should be fixed by #103561 (comment)

@exalate-issue-sync exalate-issue-sync bot added loe:medium Medium Level of Effort and removed loe:small Small Level of Effort labels Jul 27, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:large Large Level of Effort and removed loe:medium Medium Level of Effort labels Aug 11, 2021
@jloleysens jloleysens mentioned this issue Sep 30, 2021
Merged
1 task
@exalate-issue-sync exalate-issue-sync bot added loe:medium Medium Level of Effort and removed loe:large Large Level of Effort labels Dec 29, 2021
@tsullivan
Copy link
Member

This is no longer applicable after a round of fixes in screenshot capture, and the UX on presenting errors in the Reporting management pages: #103561 #120617 #118186

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:medium Medium Level of Effort
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@timroes @tsullivan @bhavyarm @elasticmachine