[Canvas] Embeddables filtered by timepicker ignore the field given by the timepicker

[stacey-gammon]

Maybe not exactly a bug but the behavior isn't clear.

The canvas time picker has a time field, but for embeddables this is being transformed to the timeRange input, not used as a filter, and this will filter on whatever field is marked at the "time" field when the index pattern object was created. This is why in #44129, near the end the data showing up in the two searches is different. One is being filtered on @timestamp one on timestamp field.

So if your data has multiple time fields, and you pick one that is not the default from the index pattern being used by the embeddable, would the user expect it to filter on the field you explicitly chose for the time picker, or the default one? Right now it filters on the default one, but I think that would be unexpected from a user perspective because they explicitly choose the field.

Not sure how to resolve that though or what the right experience is. 🤔

[elasticmachine]

Pinging @elastic/kibana-canvas

[elasticmachine]

Pinging @elastic/kibana-app-arch

[stacey-gammon]

Tagging App arch too, I think it would be interesting to discuss passing down time range as a filter and getting rid of the specific timeRange input. That would make this easier, and I think is a better long term plan since we want to get rid of reliance on index pattern objects.

[clintandrewhall]

We'll be working on this with an update to filtering between dashboards and canvas.

GitHub Selfies

[crob611]

Closing this issue as we don't strip the field off the time filters anymore. There is still some confusion around an embeddable having a time range, and also being able to use a time filter with a field, but we will track that in the overall filtering in canvas issue #88709