You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #83422, we introduced the advanced search syntax.
When filtering by type using the type:XXX syntax, we are using the SO objects technical name as term value.
For example for dashboard, you use type:dashboard.
However in some cases, the technical name of the type does not match the default label that is used in user-facing UI. For example, for canvas workpads, the name is canvas-workpad.
User would probably be searching for type:canvas or type:workpad, meaning that no result would be returned.
We should probably allow some kind of aliases when parsing the query, to convert these aliases to the actual technical name of the types.
Note that for the currently searchable types, canvas-workpad is the only one where the common label does not match the technical name.
The text was updated successfully, but these errors were encountered:
Tagging the @elastic/kibana-presentation team for awareness.
Nothing for you all to do at this point, just know that filtering will be improved via aliases.
In #83422, we introduced the advanced search syntax.
When filtering by type using the
type:XXX
syntax, we are using the SO objects technical name as term value.For example for dashboard, you use
type:dashboard
.However in some cases, the technical name of the type does not match the default label that is used in user-facing UI. For example, for canvas workpads, the name is
canvas-workpad
.User would probably be searching for
type:canvas
ortype:workpad
, meaning that no result would be returned.We should probably allow some kind of aliases when parsing the query, to convert these aliases to the actual technical name of the types.
Note that for the currently searchable types,
canvas-workpad
is the only one where the common label does not match the technical name.The text was updated successfully, but these errors were encountered: