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
Currently in a widget, if you want to know how many times a specific label is used, it would be nice to be able to filter out, after the query is done, from a display point of view onl, some data to only show data that matter.
For instance, if I have a donut filtering on all RFI with satus = closed and label = not empty, I maybe want to know the proportion of RFI having labels X or Y or Z among the results. As a result, we would need to filter out, from the result of the query, any data that does not match any filters.
Current Workaround
Proposed Solution
Additional Information
If the feature request is approved, would you be willing to submit a PR?
Yes / No (Help can be provided if you need assistance submitting a PR)
The text was updated successfully, but these errors were encountered:
nino-filigran
added
feature
use for describing a new feature to develop
needs triage
use to identify issue needing triage from Filigran Product team
and removed
needs triage
use to identify issue needing triage from Filigran Product team
labels
Jan 9, 2025
Use case
Currently in a widget, if you want to know how many times a specific label is used, it would be nice to be able to filter out, after the query is done, from a display point of view onl, some data to only show data that matter.
For instance, if I have a donut filtering on all RFI with satus = closed and label = not empty, I maybe want to know the proportion of RFI having labels X or Y or Z among the results. As a result, we would need to filter out, from the result of the query, any data that does not match any filters.
Current Workaround
Proposed Solution
Additional Information
If the feature request is approved, would you be willing to submit a PR?
Yes / No (Help can be provided if you need assistance submitting a PR)
The text was updated successfully, but these errors were encountered: