Kevin Garcia

@btzeng - can you dig into this from the UX side to find an intuitive pattern for this? @Sandy381 - we may have some additional follow-ups as we dig into...

Let's seek some additional clarity on implementation here. I think after sitting some time with this, it feels like we're creating a front-end abstraction that creates permanent objects to track...

My preference here is that a theme should have a dark/light subvariant. This is because these days, many people just use their OS settings, so I'd like to provide 2...

@kavilla - I'd like to see custom filters and custom time ranges as options for individual visualizations. @btzeng - let's explore this from a UX/Visual perspective

Are we differentiating between Dashboards users and Engine (backend) users? How do we disambiguate between a user logging into Dashboards, vs a user logging into a Cluster? Will we pass...

Similar to @zengyan-amazon's comment, is there a plan to differentiate between access control to data, vs access control to dashboards objects. For example, what happens if a visualization has been...

I'm finding myself nodding along to both @mihirsoni and @AMoo-Miki's points. I think we need to double down on core being the platform that enables features and functionality to be...

> We'll update this issue to make sure the community is clear on the change: #2088 > > But otherwise, @sipopo we agree with these changes and will plan to...

> `You're using an untested version of Node.js. OpenSearch Dashboards has been tested to work with Node.js ${requiredVersion}. Your current version is ${currentVersion}.` This works for me

There is an advanced setting in stack management that determines the date format of how dates should be pretty printed. We should be using that to format the date/time display.