[Reporting] Timezone incorrect in CSV reports in different spaces

[clintandrewhall]

Kibana version:
7.9

Elasticsearch version:

Server OS version:

Browser version:

Browser OS version:

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

Describe the bug:

This was originally reported in a discuss issue.

Timezones are not always applied equally in CSV reports from Discover, depending on space and role.

Steps to reproduce:

1. Two spaces are set up with the same, specific timezone in Advanced Settings.
2. Two users are created, one "admin" and one read-only with access to only one space.
3. The admin downloads a CSV from Discovery: the timezone is applied and the times are accurate.
4. The read-only user downloads the same CSV, the timezone is not applied, using the Browser setting instead.

If the read-only user is given kibana_admin permission, the timezone is applied and the dates are correct.

Expected behavior:

The timezone set in advanced settings for the space is universally applied.

Screenshots (if relevant):

See: https://github.com/samuelamico/ElasticSearchBugs

Errors in browser console (if relevant):

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

Any additional context:

[elasticmachine]

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

[tsullivan]

I'm not able to reproduce this issue in the main branch. Anyone else?

Please note that the SpaceID is logged in the Kibana logs for each CSV generation request.

[tsullivan]

Also, keep in mind it is easy for confusion to happen when changing Advanced Settings and using multiple browser tabs.

If you update Advanced Settings in one tab, you have to refresh all the tabs so they are updated to the change.

[tsullivan]

Closing this as we're not able to reproduce it