zachliu opened a new issue, #60590: URL: https://github.com/apache/airflow/issues/60590
### Apache Airflow version 3.1.6 ### If "Other Airflow 3 version" selected, which one? _No response_ ### What happened? In Airflow 3.1.6, the `Filter by tag` selection on the DAGs list page does not persist: * Navigating away from the DAGs list and back * Closing and reopening the browser tab The selected tag filter is cleared each time, requiring the user to re-select the tag(s). Observed behavior: * Tag selection only lives in in-memory UI state * No persistence via URL query params, browser storage, or server session Regression context * In Airflow `2.10.5`, tag filtering does persist across navigation and browser restarts. * In Airflow `2.x` this behavior is implemented server-side via Flask session storage (`flask.session["tags_filter"]`) in `airflow/www/views.py`. ### What you think should happen instead? The DAG tag filter should persist across: * Page navigation * Browser restarts This is important for usability when working with large DAG inventories or tag-based workflows. What likely went wrong During the Airflow 3.x UI migration from server-rendered Flask views to a React-based UI: * The legacy persistence mechanism (Flask session + redirect logic) was removed * No equivalent client-side persistence was introduced As a result, the DAG tag filter state is not stored in: * URL query parameters * localStorage / sessionStorage * Any server-side user preference store ### How to reproduce https://github.com/user-attachments/assets/5f631e79-58a6-431f-aba9-a5470650df5e ### Operating System LM 21.3 with docker python:3.12-slim-bookworm ### Versions of Apache Airflow Providers _No response_ ### Deployment Docker-Compose ### Deployment details _No response_ ### Anything else? _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
