Skip to content

[Meta][Lens] Tables #57709

@timroes

Description

@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.

Details 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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Feature:LensMetaTeam:VisualizationsTeam label for Lens, elastic-charts, Graph, legacy editors (TSVB, Visualize, Timelion) t//

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions