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

[Reporting] Add guidance to users on the new CSV export type #100363

Closed
tsullivan opened this issue May 19, 2021 · 2 comments · Fixed by #106184
Closed

[Reporting] Add guidance to users on the new CSV export type #100363

tsullivan opened this issue May 19, 2021 · 2 comments · Fixed by #106184
Labels
Feature:Reporting:CSV Reporting issues pertaining to CSV file export impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:large Large Level of Effort needs-team Issues missing a team label

Comments

@tsullivan
Copy link
Member

For 7.13, #88303 adds a new export type, export_types/csv_searchsource, for saving a search as CSV. It takes advantage of a more efficient and future-proof way to serialize the search params.

Meanwhile, the "old" CSV export code still exists in export_types/csv for backwards compatibility. If users have created automated CSV exports through Watcher in 7.12 or lower, their report jobs use the "old" parameters, and will only continue to work until 8.0.

Before then, we want them to migrate to export_types/csv_searchsource for 8.0 compatibility.

  1. Make sure there are warnings logged in the Kibana server logs when an export_types/csv job is created.
  2. Add a tooltip to the Reporting Management UI to notify users about reports that were created using legacy job params
  3. Use the deprecation service to alert admins before upgrading to 8.0 if they have existing CSV reports that were created using legacy job params.
@tsullivan tsullivan added EnableJiraSync (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead labels May 19, 2021
@elasticmachine
Copy link
Contributor

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

@elasticmachine
Copy link
Contributor

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

@exalate-issue-sync exalate-issue-sync bot added impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:small Small Level of Effort labels May 23, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:medium Medium Level of Effort and removed loe:small Small Level of Effort labels Jun 1, 2021
@tsullivan tsullivan changed the title [Reporting] Migrate users to the new CSV export type [Reporting] Add guidance to users on the new CSV export type Jun 21, 2021
@exalate-issue-sync exalate-issue-sync bot added loe:large Large Level of Effort and removed loe:medium Medium Level of Effort labels Jul 8, 2021
@sophiec20 sophiec20 added Feature:Reporting:CSV Reporting issues pertaining to CSV file export and removed (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead (Deprecated) Team:Reporting Services labels 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
Feature:Reporting:CSV Reporting issues pertaining to CSV file export impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:large Large Level of Effort needs-team Issues missing a team label
Projects
None yet
3 participants