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 report is using timezone from default Space instead of the current Space #70175

Closed
immon opened this issue Jun 29, 2020 · 5 comments · Fixed by #76998
Closed

CSV report is using timezone from default Space instead of the current Space #70175

immon opened this issue Jun 29, 2020 · 5 comments · Fixed by #76998
Assignees
Labels
bug Fixes for quality problems that affect the customer experience (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead

Comments

@immon
Copy link

immon commented Jun 29, 2020

Kibana version: 7.8.0

Elasticsearch version: 7.8.0

Server OS version: ubuntu 18.04

Browser version: firefox 77

Browser OS version: ubuntu 18.04

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

Describe the bug:

CSV report does use timezone from default Space instead of the current Space.

Steps to reproduce:

  1. Create index with one document
POST myindex/_doc
{
  
  "@timestamp": "2020-06-29T12:00:00Z",
  "messages": "utc noon"
}
  1. In the default Space change dateFormat:tz to Europe/Warsaw
  2. Create new Space with dateFormat:tz set to US/East
  3. In the default Space create index pattern and in Discover find the document. Save search, and generate CSV report.
  4. Report generated in default space does include correct timestamp:
"@timestamp","_id","_index","_score","_type",messages
"Jun 29, 2020 @ 14:00:00.000","t6xo_3IB62SZoyLfRA1w",00569380,,"_doc","utc noon"
  1. Switch to newly created Space and repeat steps from 4 in this space.
  2. In Discover document has correct timestamp listed: @timestamp: Jun 29, 2020 @ 08:00:00.000 messages: utc noon however CSV report includes timestamp "Jun 29, 2020 @ 14:00:00.000" which is incorrect.
    Timestamp in CSV should be 8:00 since it's US/East timezone but it's 14:00 as per timezone from default Space.

This bug is different from #56497 since I don't use Browser as a timezone.
Might be related to #68718

Expected behavior:

CSV report should use current space timezone.

Screenshots (if relevant):

Errors in browser console (if relevant):

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

Any additional context:

@lukasolson lukasolson added (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead Team:Reporting Services triage_needed labels Jul 2, 2020
@elasticmachine
Copy link
Contributor

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

@tsullivan
Copy link
Member

Similar to #68076

@Dosant
Copy link
Contributor

Dosant commented Dec 4, 2020

@tsullivan, I think this wasn't fixed by #76998.

Reproduced in 7.9.1 and master:

  1. Create a space and set some custom timezone for that space
  2. Export CSV.
  3. See dates in timezone from default space

@Dosant Dosant reopened this Dec 4, 2020
@Dosant Dosant added the bug Fixes for quality problems that affect the customer experience label Dec 4, 2020
@elasticmachine
Copy link
Contributor

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

@tsullivan
Copy link
Member

Replacing with #84717

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 (Deprecated) Feature:Reporting Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants