Kibana advanced setting is getting removed after version upgrades

[amitripshtos]

Kibana version:
4.5/4.6

Elasticsearch version:
2.3.5/2.4

Server OS version:
centos 7

Browser version:
chrome 52

Browser OS version:

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

Description of the problem including expected versus actual behavior:
I`m having a problem where you change the timezone setting in kibana to America/New_York, then upgrading kibana to a newer version.

After the upgrade, the parameter is being changed back to Browser.

Steps to reproduce:

1. change advanced setting dateFormat:tz to America/New_York
2. upgrade kibana version
3. see that dateFormat:tz is back to Browser

Errors in browser console (if relevant):

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

Describe the feature:

[jbudz]

Advanced settings are stored in the .kibana index in elasticsearch. Is it possible this was removed when upgrading elasticsearch? I was't able to reproduce this locally.

[amitripshtos]

OK I did missed a thing:
I have kibana-per-user environment, by creating ".kibana" for each user and routing him thorugh a personal NGINX proxy.

so when userA logs to kibana, he will send HTTP requests to index ".kibana" , but it will change to ".kibana-usera"

So I guess kibana server does something to ".kibana" index while not changing ".kibana-usera" and that`s why the bug is happening, am I right?

[jbudz]

Yes, kibana's advanced settings are id'd by the current kibana version. When upgrading, kibana will transfer the previous version's config to the new version. It likely isn't accounting for per user indices.

I'm going to close this for now because this isn't something explicitly supported by kibana and likely falls under #3904. Let me know if there's something missing here and I'll reopen.