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

Preview mode for report generation #18015

Closed
elasticmachine opened this issue Jul 19, 2017 · 4 comments
Closed

Preview mode for report generation #18015

elasticmachine opened this issue Jul 19, 2017 · 4 comments
Labels
(Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead enhancement New value added to drive a business result Feature:Reporting:Framework Reporting issues pertaining to the overall framework impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:x-large Extra Large Level of Effort needs-team Issues missing a team label

Comments

@elasticmachine
Copy link
Contributor

Original comment by @alexfrancoeur:

Many of our customers are surprised to see the layout of our PDF report after generating one. At the moment, we do not give them any control over this. As we begin to introduce features like LINK REDACTED, we could begin to provide previews of what their report would look like when exported to PDF, before saving and scheduling.

When discussed, Chrome's print preview UI is usually referenced

screen shot 2017-07-19 at 8 43 33 am

Initial implementation

  • Preview mode would show how the PDF will look like when it's exported and generated
  • It should also show where pagination occurs, possibly with a red line where the page ends

This will be a dramatic improvement to a users current experience of generating the report and allow them to proactively make improvements.

Subsequent phases

  • I'd like to get to the point where where we become a bit more intelligent about pagination and rather than cutting off the report mid-visualization, we dynamically sort the report layout so that it fits the PDF.
  • No matter how nicely we pre-package this report users will want to customize the layout as they see fit. It would be nice to have the ability to configure a "report layout" for a dashboard through this preview mode.

cc: @elastic/kibana-sharing, @snide

@elasticmachine elasticmachine added :Sharing (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead labels Apr 24, 2018
@timroes timroes added Team:Visualizations Visualization editors, elastic-charts and infrastructure and removed :Sharing labels Sep 13, 2018
@timroes timroes added Team:Stack Services and removed Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Jul 18, 2019
@bmcconaghy bmcconaghy added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team:Stack Services labels Dec 12, 2019
@elasticmachine
Copy link
Contributor Author

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

@tsullivan tsullivan removed the Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) label Dec 17, 2020
@elasticmachine
Copy link
Contributor Author

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

@tsullivan tsullivan added the enhancement New value added to drive a business result label Feb 25, 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 May 13, 2021
@tsullivan
Copy link
Member

We could achieve this by separating out the screenshot and layout definition modules from Reporting, and use them to create a "one-off" screenshot that isn't connected to a report.

The solution is similar to #55622 (comment)

@exalate-issue-sync exalate-issue-sync bot added loe:weeks and removed loe:small Small Level of Effort labels May 13, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:x-large Extra Large Level of Effort and removed loe:weeks labels Dec 2, 2021
@ppisljar
Copy link
Member

ppisljar commented Aug 9, 2022

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.

@ppisljar ppisljar closed this as not planned Won't fix, can't repro, duplicate, stale Aug 9, 2022
@sophiec20 sophiec20 added the Feature:Reporting:Framework Reporting issues pertaining to the overall framework label Aug 21, 2024
@botelastic botelastic bot added the needs-team Issues missing a team label label Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
(Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead enhancement New value added to drive a business result Feature:Reporting:Framework Reporting issues pertaining to the overall framework impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:x-large Extra Large Level of Effort needs-team Issues missing a team label
Projects
None yet
Development

No branches or pull requests

7 participants