messere1 opened a new issue, #2168: URL: https://github.com/apache/rocketmq-dashboard/issues/2168
## Problem Operators who switch repeatedly among many RocketMQ instances must search the full selector every time. This adds friction across topic, consumer, message, ACL, DLQ, and resource-plan workflows. ## Proposal Remember a small, browser-local list of recently selected instances and surface valid recent entries first in the shared InstanceSelect component. Stale or inaccessible instances must be pruned, and storage failures must not break selection. ## Acceptance criteria - Recently selected instances are persisted locally and displayed first. - Recent and remaining instances are clearly grouped in English and Chinese. - Removed or inaccessible instances never remain selectable through history. - Clearing and selecting preserve existing component behavior. - Persistence and grouping are covered by frontend tests. Target branch: rocketmq-studio. -- 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]
