You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature:
The 'Recently viewed' section of the left hand nav is a handy way to navigate Kibana and reduce navigation efforts for our users. That said, the current use of local storage (while we await a proper personalization solution) present some quirks if/when a user signs in using multiple accounts or if users were to share a computer/browser.
Describe a specific use case for the feature:
One way we could partially mitigate this situation in the short term would be to provide a 'Clear recents' link or button in that section of the nav.
More can certainly be done, but this feels like a nice improvement that will remain useful even into the future once a personalization backend is available.
The text was updated successfully, but these errors were encountered:
I think the best alternative would be have another saved object - per elastic user? And kibana can use the add/remove api internally to fetch it
That way, if a computer is shared, those errors are removed. Additionally, recent views would roam with the user, instead of being browser/pc specific.
Related to #67083 #72836
Describe the feature:
The 'Recently viewed' section of the left hand nav is a handy way to navigate Kibana and reduce navigation efforts for our users. That said, the current use of local storage (while we await a proper personalization solution) present some quirks if/when a user signs in using multiple accounts or if users were to share a computer/browser.
Describe a specific use case for the feature:
One way we could partially mitigate this situation in the short term would be to provide a 'Clear recents' link or button in that section of the nav.
More can certainly be done, but this feels like a nice improvement that will remain useful even into the future once a personalization backend is available.
The text was updated successfully, but these errors were encountered: