Search is silently persisted when saving Filters

[proddata]

Describe the issue

When saving Filters, the current Search value is also persisted. However, this is not visible or communicated in the UI.

Search is a separate control from structured filters:

• It is not added via Add Filter
• It is not shown as a filter chip
• It cannot be removed the same way as other filters

As a result, users can load a saved filter and see fewer rows than expected, with no indication that a search term is still applied. This creates “ghost filters” that are hard to discover and debug.

From a user’s point of view:

• Filters are explicit, structured, and visible
• Search looks transient and ad-hoc

But under the hood they are both treated as part of the saved query, which breaks the mental model.

Expected behavior

There are two coherent options:

Option A — Treat Search as part of saved filters

• Persist the search term when saving a filter
• Display it as a visible filter (e.g. a Search: <term> chip)
• Allow users to remove or edit it like any other filter

Option B — Treat Search as transient

• Do not persist the search term when saving filters
• Keep Search as a temporary, session-only narrowing tool

Environment

• Kestra Version: develop

[bluemeaford]

This makes sense — saving “Search” silently creates a ghost filter. I’m happy to open a PR. Do maintainers prefer Option A (persist search and show it as a removable chip) or Option B (don’t persist search when saving filters)?

[Ms-Kulkarni]

Hey @MilosPaunovic can i work on this issue?

[chintamani-pala]

Hey @proddata can i work on this issue?

[MilosPaunovic]

@bluemeaford I've assined you to the issue, but let's wait for a decision from the @kestra-io/products team on which approach to take here. 🚀

For all the others, if you're still willing to contribute, may I suggest that you check our curated list of good first issues to see if there is something you find interesting enough and think you can tackle independently. It can be further filtered by desired labels to narrow down the results (suggesting to filter by either area/backend, area/plugin or area/frontend ones, based on your preferences).

[Ben8t]

Discussed with @proddata : let's go for Option B, i.e. "Do not persist the search term when saving filters", "Keep Search as a temporary, session-only narrowing tool"

[MilosPaunovic]

@bluemeaford You can proceed now with the option B.