[Meta][Lens] Tables

[timroes]

This meta issue tracks the workstream of improving tables in Lens.

For this workstream we are considering the following use cases:

• Table as a data discovery tool
• Table as a visualization on the dashboard - primary use case

We are not considering table we may show in the UI as part of the editor experience or inspector.

• Rename "break down by" to "rows" Change break down by in Lens table to rows #83335
• Switch to data grid [Lens] Replace basic table with EuiDataGrid #72504
• Summary row [Lens] Support summary row for table #84558
• Transpose rows and columns [Lens] In table visualization, users can transpose rows into columns #69450
• Gradient coloring [Lens] Gradient colors for numeric table cells based on palette #68428
• Creating custom stops for table coloring [Lens] Custom gradient colors for numeric table cells #66192
• Hierarchical header (grouped columns) [Lens] Hierarchical header for splitted columns in data table #94433
• Grouped rows [Lens] Tables with grouped rows to improve readability #61470
• Align columns left/right/center Kibana Data Table: Provide an option to align data (horizontal : left, center or right, vertical : up, center, down) on each data column #14524
• Hide column [Lens] Allow hiding of columns in table #85140
• Allow filtering by a last value column [Lens] Table: Allow filtering last value cells #94438
• Pagination [Lens] Table pagination #96778
• Dynamic coloring - overall gradient vs split by column [Lens] Table dynamic coloring: compute overall gradient for split columns #96401
• [Lens] Table drag and drop duplicate does not copy styling over #113269
• Kibana feature : Allow users to display a string with newlines inside the datatable #76242
• Sparklines #3395
• Improve sorting in edge cases [Lens] Improve sorting for aggs with custom labels #88172
• Cell contents can be clickable for drilldowns [Lens] Allow cell contents to be clickable when drilldowns are enabled #102115
• [Lens] make data table selectable #106436
• [Lens] Allow sorting on dashboard edit & view #114625
• [Lens] Align "row height" terminology to Discover, custom row heights #123654
• Pivot columns [Lens] Pivot columns #61489
• Grouped rows [Lens] Tables with grouped rows to improve readability #61470
• Dynamic coloring - overall gradient vs split by column [Lens] Table dynamic coloring: compute overall gradient for split columns #96401
• [Lens] Auto height setting for table #115582
• [Lens] Update name of "Columns" to something more descriptive #134576
• [Lens] Make metric columns filterable in table #139083
• Server side sortable table columns [Lens] Server side sortable table columns while in edit mode #55905
• [Lens] Data Table Rotate 90°  #141270

Prior discussion:

Basic Expectations/Short term roadmap

• Setting sort order by the values in the column as part of editor: user can specify how the data will be sorted in the visualization: improve the UX to allow user to click on the column header [Lens] Server side sortable table columns while in edit mode #55905
• Friction point: when another columns is added, it should go on the right and be a subdivision of the prior results
  • Aggregation order and column order should be consistent
  • Technically depends on some refactoring and arch changes; related to drag-and-drop reordering
  • Can build out a prototype to test the interation
  • Will be incremental improvement over med term
  • Change should not affect other chart types (bar/area charts)
• Friction point: cannot reorder the columns, user has to remove them and add again
  • Same as above, but if we can fix this without the other it would be helpful

Feature needs/Longer term roadmap

• Ability to change the sort order of an existing Lens vis from dashboard & retrieve new data sorted correctly
  • Server-side sorting
  • Need variables in expressions to work
  • Dependency on AppArch team
  • Future, not near term
• Client-side sorting: user can click on the column in a data vis and resort already retrieved data by a column
  • Don't do: because user may get incorrect data and are not aware of it
• Filtering the table results
  • Interaction with the global filters/search: already in flight, no additional requirements
  • Generic bucket filtering for all vs is part of data retrieval
• Exporting as CSV
  • Should have export buttons similar to data table
  • Improve UX - take up less real estate, maybe put in the action panel?
  • Ability to export should be based on user having the right role: proposal is to add export to csv as a sub-feature of the reporting role
  • (maybe) Allow users to show or hide export capabilities
  • Technically small-medium change
• Conditional formatting of values
  • Colored backgrounds, font color
  • Technically small-ish change. Start with colored background.
• Pagination vs infinite scroll?
  • For reporting (PNG export, for example) may need to see all results
  • Not in the short term
• Summary row/column showing totals
  • Short term, highly valuable
  • Minor questions about design & functionality (do we summarize over the whole table or current page?)
  • Should figure out how to implement this within data grid (even if we decide to build this on top of nested or pivot tables)
• Pivot tables
  • Highly requested feature and would be a headline for a release
  • Dependency on the data grid component & search infrastructure
• Drill-down support
  • Drill-downs in dashboard will be working once we have drilldown infrastructure in place
  • Drill-downs within the table: expand details

To be discussed

• Displaying hierarchies such as Category -> Sub-category or Year -> Month
• Nested tables for hierarchical data
• Calculated columns
• Custom actions
• Cell-level visualization widgets such as a trend indicator or sparkline (Sparklines #3395)
• Widgets could also include health indicators, gauges, links to actions
• Friction point: ability to have tables without metrics
  • Not currently supported in the querying infrastructure
• Friction point: align currency to the right - drives BA users crazy that it is currently aligned to the left

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[beanaroo]

Can we please consider adding the option to specify which column can be wrapped and which shouldn't be wrapped? The below screenshot exhibits a lot of wasted whitespace:

[flash1293]

@beanaroo The next version of Kibana (7.12) will include an improved data table allowing you to resize the columns as desired which can be used to control the wide space (#88069)

However, this means that columns won't wrap anymore at all. If that's an important feature for you, please open a separate issue for this and ping me there (as this is supposed to be a list of more detailed issues)

[timductive]

Closing old meta issues in favor of more granular, current meta issues