Fix 10292

[prathamesh-patil-5090]

Abstract

Fixes #10292

When applying a filter, search, or sort on the Tasks page, the browser history entry was being replaced (history.replace) instead of pushed. This meant the Back button would navigate away from the Tasks page entirely instead of restoring the previous filter state.

Changes

• tasks-page.tsx: Introduced a setQuery callback (mirroring the pattern from the Jobs page, Flattening job list on a task page #10217) that:
  • Calls history.push when filter, search, or sort changes — so
    each filter change creates a new history entry and Back restores it.
  • Calls history.replace when only page/pageSize changes — pagination
    does not pollute the history stack.
• Added a useEffect on [updatedQuery, query, isMounted] to re-fetch tasks when the URL changes (e.g., via Back/Forward navigation), keeping data in sync with the URL.
• All handlers (onApplyFilter, onApplySearch, onApplySorting, Pagination.onChange) now route through setQuery instead of dispatching directly.

Testing

1. Go to the Tasks page.
2. Apply a filter/search/sort — note the URL updates.
3. Apply a second, different filter.
4. Press the browser Back button — the previous filter state should be
   restored and the task list should update accordingly.
5. Press Forward — the later filter state should be re-applied.
6. Changing only the page number should not add a new history entry.

Related

• Closes Pressing back button in browser should apply previous filter state #10292
• Follows the same approach introduced for the Jobs page in Flattening job list on a task page #10217