CSV report is using timezone from default Space instead of the current Space #70175
Labels
bug
Fixes for quality problems that affect the customer experience
(Deprecated) Feature:Reporting
Use Reporting:Screenshot, Reporting:CSV, or Reporting:Framework instead
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:
dateFormat:tz
toEurope/Warsaw
dateFormat:tz
set toUS/East
@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:
The text was updated successfully, but these errors were encountered: