Default aggregation type for a field in an index pattern

[shaunmcgough]

Currently, there is no sticky, reliable way to use a default aggregation type for a field. This requires many more clicks, and a not so great user experience.

Use case:
Actor: User
Actions: User goes into an index pattern, and is able to add a default aggregation type to each field that is marked aggregatable.

In Lens, or any other visualization, this aggregation will be the default, every time the field is used.

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServices)

[mattkime]

@shaunmcgough Is this something you want to be selected by the user or would it be predefined somehow? Just want to make sure I understand the common user experience.

[shaunmcgough]

For now, anyone with index pattern editing access could set it. I do like the idea of predefining this, but that is maybe a bit too predictive in most scenarios. I could see predefining working for ECS though, or known datastreams. Make sense?

[mattkime]

Make sense?

Definitely.

I'd like to make sure I'm prioritizing this correctly. Could this be tied to a larger goal or is it a 'nice to have'?

[elasticmachine]

Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations)

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[kertal]

Closing, since it's been a while since this was created, and last interaction has been nearly 3 years ago. Feel free to reopen if you think we should implement this feature

[markov00]

Tracking request in Lens general improvements ice box #184459