Allow switch between legacy table and EuiDataGrid: Add an option to enable or disable the EuiDataGrid (2.11 table) for user preference.

[ananzh]

Propose to provide two ways for customer to switch between legacy table and data grid table.

• Use a new advanced settings Use legacy table

• Use the switch table toggle on Discover page

[ashwin-pc]

@ananzh Can we make both the toggle behave the same way? Right now it looks like one toggle activates the legacy table when turnd on and the other activates the new table when turned on.

Also i'd probably call it newDiscoverExperience. This lets us bundle all the changes into one instead of just the table. @shanilpa @dagneyb what do you think?

[shanilpa]

@ananzh I like that we have the setting accessible through advanced settings as well as in the application (plus 1 Ashwin's comment)

I do have additional feedback for the in app toggle. It feels detached from the component that is changing (which is okay) if we provide a description on what the change could entail. Additionally, we are missing the chance to collect feedback on the new table. Here is my suggested UX for enabling new features we would like users to try.

New.features.mp4

cc @kgcreative, @ashwin-pc, @dagneyb

[ananzh]

@ashwin-pc I see. Good point. Will modify the advanced settings to Use new table. Regarding newDiscoverExperience, you mean the toggle on the discover page? or in the advanced settings description? I would recommend New table since only table is updated. The side nav is updated as well as query/filter bar position.

[ananzh]

@shanilpa @ashwin-pc Thanks for the quick feedbacks. Let me summarize what we need to change:

• Change Use Legacy table to Use New table and modify descriptions accordingly. So default is disabled/off for both toggle and advanced settings.
• Change New table toggle to Try new Discover features. When click it, it will pop up a helper with 1) similar descriptions as in advanced settings 2) Enable new table 3) Share feedbacks on github and link to https://github.com/opensearch-project/OpenSearch-Dashboards/issues

[dagneyb]

@ananzh sounds good on the update to the advanced settings phrasing to align with the in-line selector. I agree with @shanilpa 's feedback that we should bring the toggle closer on the UI to the element it is impacting. I'm not fully aligned with the UI @shanilpa proposed in the video above however. The goal should be that we dont have multiple features being enabled/disabled at a given time, we should keep it really simple for each release with 2 options, not giving an on/off switch for all features. With that said, could we align on a toggle experience that makes it more obvious in this release that it controls the table, and if we use a toggle in a future release to try out a new Discover experience with multiple changes, that toggle would go back to the high level location proposed in the original issue here. Thoughts?

[ananzh]

I think Enable new table is the only option right? Enable new feature is just something we might expand in the future right?

@shanilpa and @dagneyb could we make a decision whether we want to use a single toggle or something like the mock with only one Enable new table?

[shanilpa]

@dagneyb we can have a checkbox in the modal that says enable all new features so users can select all without having to click individually. I do think the granular control has several benefits:

1. User transparency on what is going to change and to what (especially if we bundle changes in Discover)
2. Allows users to pick and chose what functionality they would like based on their workflows (it isn't all or nothing)
3. Allows deep links if users want to provide feedback on a specific change

For this specific change since it is only the table if we can have the control closer to the table like in the original issue I think that works: #5555 (comment) (plus it sounds like users are okay with the placement of the toggle there)

[ananzh]

Since table is only switchable component and given a tight timeline to mitigate users pain, we will keep a simple toggle to avoid any complexity and confusion. Meanwhile, we already have an established feedback mechanism (accessible via the ? icon) that our customers are familiar with. This feature has been a part of OSD from the start. We won't introduce a separate feedback channel specifically for the new Discover which might lead to redundancy. Based on the discussion, I would like to confirm the changes

• Keep toggle but change New table to New Discover Experience (@shanilpa Is this too long? Would like to have ur confirmation.) in the top nav as shown in the above.
• Add a dismissable notice (@shanilpa which way you prefer?)
  • Add notive like we did in 2.10 that lets the user know about the toggle and also points to them that they could click ? to provide feedback.
  • Add a notice like we did in 2.10? because customer should be familiar with our feedback loop.
• Change Use Legacy table to Use New table and modify descriptions accordingly in the advanced settings. So default is disabled/off for both toggle and advanced settings.