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

[6.7] Don't save the current timezone in visualizations (#34795) #34927

Merged
merged 5 commits into from
Apr 15, 2019

Conversation

timroes
Copy link
Contributor

@timroes timroes commented Apr 11, 2019

Backports the following commits to 6.7:

* Don't save the current timezone in visualizations

* Add additional test

* Add test and switch migration number

* Don't clone object according to review feedback

* Better documentation

* Update src/legacy/core_plugins/kibana/migrations.js

Co-Authored-By: timroes <[email protected]>
@timroes
Copy link
Contributor Author

timroes commented Apr 11, 2019

@chrisdavies @lukeelmers since the backport was a lot of manual work, I would appreciate another quick glance over this 6.7 backport to check if everything seems okay to you.

@elasticmachine
Copy link
Contributor

💔 Build Failed

@timroes
Copy link
Contributor Author

timroes commented Apr 11, 2019

Jenkins, test this - I think a legit failure, just want to make sure

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💔 Build Failed

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

@timroes timroes merged commit 5e86ec3 into elastic:6.7 Apr 15, 2019
@timroes timroes deleted the backport/6.7/pr-34795 branch April 15, 2019 09:16
@lukeelmers
Copy link
Member

@timroes sorry i didn't respond to this - fwiw i did review the code again to make sure it looked okay, but just hadn't pulled it down to test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants