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

CSV export date not applying correct date format (from a saved search in a dashboard) #56153

Closed
daohodac opened this issue Jan 28, 2020 · 6 comments
Labels
Feature:Reporting:CSV Reporting issues pertaining to CSV file export needs-team Issues missing a team label

Comments

@daohodac
Copy link

Kibana version:
7.5.1
Elasticsearch version:
7.5.1
Server OS version:
debian 9
Browser version:
chrome
Browser OS version:
78.0.3904.108
Original install method (e.g. download page, yum, from source, etc.):
.deb
Describe the bug:
Try to export a saved search from a dashboard as CSV. The CSV is correct but the format of the @timestamp is not OK for my customer because excel does not accept 2020-01-21T07:52:51.000Z which is the format I get (ISO8601).
image

I tried to change the format in the General Settings / Date format without effect.

image

The @timestamp should apply the Date format or there should be a way to specify the export format

Steps to reproduce:

  1. create a saved search
  2. add it to a dashboard
  3. click on the top right gears (see snapshot herabove)
  4. select download CSV
  5. look at the @timestamp column (first one). The date is in the format 2020-01-21T07:52:51.000Z
  6. go to Management / advanced settings / Date format and set YYYY-MM-DD HH:mm
  7. back to the dashboard, download the CSV. The @timestamp is still in ISO8601 format

Expected behavior:
The @timestamp should be in the YYYY-MM-DD HH:mm format in the exported CSV

Screenshots (if relevant):
image

Errors in browser console (if relevant):

Provide logs and/or server output (if relevant):

Any additional context:

@omarsar
Copy link

omarsar commented Jan 28, 2020

I can also confirm this behavior. The export works well when done in the context of "Discover" but fails to apply the new format when done in the context of a "Dashboard". It's unexpected behavior. Hopefully, this is an easy fix. Thanks for posting @daohodac.

@wylieconlon wylieconlon added (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Team:Reporting Services labels Jan 28, 2020
@elasticmachine
Copy link
Contributor

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

@tsullivan
Copy link
Member

Thanks for filing this. It looks like a valid bug.

@tsullivan
Copy link
Member

This can be fixed for the "date" type of fields, but it looks like fixing "date_nanos" will require similar work as #30264

@tsullivan
Copy link
Member

Fixed in #67027

Fixes Download CSV showing raw data instead of formatted per the index pattern

@tsullivan
Copy link
Member

Closed in #67027

@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 needs-team Issues missing a team label
Projects
None yet
Development

No branches or pull requests

6 participants