Combine default filter with users filter

[Buckwich]

Is your feature request related to a problem? Please describe

In bpmn we use the default filter to remove some unrelated repos from our task board. But if a user enters a custom query that filter no longer applies and I have to combine the default filter and my filter manually

Eg:

• https://tasks.bpmn.io/board?c=%21Inbox contains no form-js issues
• https://tasks.bpmn.io/board?c=%21Inbox&s=is%3Aunassigned+ does contain them

Describe the solution you'd like

I would like an easy way to combine the default filter with the user filter. This could be a simple toggle button similar to vscode exclude filter toggle:

Describe alternatives you've considered

just combine the filters by default. Maybe this is also a bug and that was the intended behavior

Additional context

If you agree that that would be a nice feature to have I could work on it myself

[nikku]

Could you elaborate on the use-case? My thought on the current behavior is: Default filter is really a default filter, once I search for a particular repository or term, I still see the filtered per default elements in the list. It would be unintuitive for me to to never see such items.

[Buckwich]

It would be unintuitive for me to to never see such items.

Thats why I want it to be a toggle button

Could you elaborate on the use-case?

cf. our bi-weekly meeting

most of the time we are on the taskboard and apply different filters during the session so the default filter basicly never applies, and with that the number of items can be a bit overwhelming making it easier to miss stuff. Another issue of the default filter is that i don't know what it is from the webapp (i need to look into the current config to know)

also for inbox grooming (if you for some reason filter it):

default filter: 24 inbox, 1263 backlog
is:unassigned: 42 inbox, 1306 backlog

[nikku]

i need to look into the current config to know [the filter, and sometimes I don't even have access to "the config"]

I agree to your points that the default filter is not discoverable, and the solution you showcase (VSCode) seems to be reasonable; it could indicate on hover the default filter.

If we go this route, let's ensure it is part of the link, the context must be preserved on shares. Happy to take a PR to incorporate this.

We could consider for a moment the security implications, does it hurt to show the filter to everyone?

[barmac]

Alternative proposal: Have a shorthand for the default filter, e.g. @defaultFilter is:unassigned. This way we don't change the current behavior, but allow to use the default filter easily.