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
Imagine you are looking at a service metrics dashboard for an env staging and you want to see the same for different env prod, now if you change the deployment_environment variable to prod all the dependent variable selection gets reset to ALL. This can be an annoying experience because I have to make the same selection as earlier.
Should we not reset all the times or should we not reset only when the newly fetched values have the previous selection as a subset? i.e only reset the service_name if the result of service_name for new env returns a set that has no common values in current selected value?
The text was updated successfully, but these errors were encountered:
Ability to type the custom value. The value should be applied on the enter key or move the mouse out
For single select only one value
For multi-select, more than one value
Push the selected values to the top
Do not close the dropdown for multi-select after the first selection
Separate ALL from the rest of the options.
One should be able to select multiple at the same on the first load. Right now ALL is enabled by default and one can’t go about selecting more than one.
Do not reset the filter to default when the response already contains the selected values i.e. keep the existing values chosen if they are also present in the response.
Be able to clear the selection
Easy to edit mode when the number of selected values is high
The sequence of the queries is not going to go away
Imagine you are looking at a service metrics dashboard for an env
staging
and you want to see the same for different envprod
, now if you change thedeployment_environment
variable toprod
all the dependent variable selection gets reset toALL
. This can be an annoying experience because I have to make the same selection as earlier.Should we not reset all the times or should we not reset only when the newly fetched values have the previous selection as a subset? i.e only reset the
service_name
if the result ofservice_name
for new env returns a set that has no common values in current selected value?The text was updated successfully, but these errors were encountered: