Frun1na opened a new issue, #4579: URL: https://github.com/apache/rocketmq-dashboard/issues/4579
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository and believe that this is not a duplicate. - [x] This is a defect in RocketMQ Studio, not a usage question and not a defect in another Apache RocketMQ repository. - [x] I can reproduce this on the current `master` branch, or I have stated the exact version I am running below. ### Studio Version branch: `master`, git commit id: `d50ffecc` ### Runtime Environment Ubuntu 24.04, current Chrome. Frontend-only defect, reproduced against the dev server. ### Connected RocketMQ Cluster Any instance; the bug is in the page's scope-reset logic, not in a specific cluster. ### Build Toolchain _No response_ ### Describe the Bug On the DLQ page, the group search input keeps its value when the selected instance changes. The instance-scoped reset clears rows, pagination, selection and dialogs, but not the search term, so the first `listDLQGroups` request for the new instance still carries the old term. The user sees an empty or filtered list for the new instance without having searched anything on it. ### Steps to Reproduce 1. Open the DLQ page for instance A and type a term into the group search box that matches only A's groups. 2. Switch the instance selector to instance B. 3. Observe the group list for B. ### What Did You Expect to See? Instance B's full DLQ group list, with the search box cleared. ### What Did You See Instead? The list is filtered (typically empty) by the term typed against instance A, and the search box still shows it. ### Additional Context Draft fix in PR #4577: the reset block also clears the search term, plus a regression test. Related fixes in the same family: #4240 (client column filters), #4465 (hidden topic/consumer selections). ### Are You Willing to Submit a Pull Request? - [x] Yes, I am willing to submit a pull request. -- 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]
