Is it a UX bug applying $variables in Dashboard?

andreabisello — Fri, 05 Dec 2025 11:10:23 GMT

creating a widget in a custom dashboard,

Consider that DQL

fetch logs
| filter not matchesValue(content, array($IGNOREDERRORS))

Consider that $VARIABLE

The options are effecting the filter choosing the values required

but let's suppose i want to empty the options in the $Variable, they became unavailable

but they still effecting the filters

even if i refresh the ux, they stay set, even if i reload the dashboard, removing all the query param from the url.

only if i go with "reset to default" they really go away,

but probably in the moment in which i manually change values of $variable, the UX should "reset to the default" by itself and then reload it.

Re: I think there is a UX bug applying $variables in Dashboard

JuliaHaas — Mon, 17 Feb 2025 10:16:54 GMT

Hi @andreabisello

That is done by design. If you remove the query param from the URL or reload the page, you'll still see the variable values since they're stored in the user app state. So by removing the options, the variable values are not affected.

topic Re: I think there is a UX bug applying $variables in Dashboard in Dashboarding

Is it a UX bug applying $variables in Dashboard?

Re: I think there is a UX bug applying $variables in Dashboard