You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "messere1 (via GitHub)" <gi...@apache.org> on 2026/08/14 05:50:00 UTC
[I] [studio][Feature] Surface recently used instances in the global instance selector [rocketmq-dashboard]
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: commits-unsubscribe@rocketmq.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [studio][Feature] Surface recently used instances in the global instance selector [rocketmq-dashboard]
Posted by "RockteMQ-AI (via GitHub)" <gi...@apache.org>.
RockteMQ-AI commented on issue #2168:
URL: https://github.com/apache/rocketmq-dashboard/issues/2168#issuecomment-5290133545
**Issue Evaluation**
Category: `enhancement` | Status: **Evaluated**
**Feasibility:** feasible
**Scope:** Studio UI — global instance selector component
**Compatibility:** No breaking changes; additive UX feature
Good UX improvement. Remembering recently used instances (cluster/namespace) in the global selector reduces repetitive navigation. The proposed approach (localStorage-based MRU list, capped at 5-10 entries) is the standard pattern.
Implementation notes:
- Use `localStorage` with a namespaced key (e.g., `studio:recent-instances:<userId>`) to avoid conflicts
- Consider syncing recent instances across devices if Studio has user accounts
- Show a visual indicator (e.g., clock icon) to distinguish recent items from the full list
- Handle the case where a recent instance no longer exists (stale entry cleanup)
**Recommendation:** proceed — low complexity, meaningful UX improvement for multi-cluster users.
---
*Automated evaluation by github-manager-bot*
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [studio][Feature] Surface recently used instances in the global instance selector [rocketmq-dashboard]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] closed issue #2168: [studio][Feature] Surface recently used instances in the global instance selector
URL: https://github.com/apache/rocketmq-dashboard/issues/2168
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [studio][Feature] Surface recently used instances in the global instance selector [rocketmq-dashboard]
Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.
github-actions[bot] commented on issue #2168:
URL: https://github.com/apache/rocketmq-dashboard/issues/2168#issuecomment-5376661426
This issue has been automatically closed because there has been no activity for 7 days. If you believe this issue is still relevant, please reopen it with updated information.
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [I] [studio][Feature] Surface recently used instances in the global instance selector [rocketmq-dashboard]
Posted by "RockteMQ-AI (via GitHub)" <gi...@apache.org>.
RockteMQ-AI commented on issue #2168:
URL: https://github.com/apache/rocketmq-dashboard/issues/2168#issuecomment-5290130472
**Issue Evaluation**
Category: `enhancement` | Status: **Evaluated**
**Feasibility:** feasible
**Scope:** Studio UI — global instance selector component
**Compatibility:** No breaking changes; additive UX feature
Good UX improvement. Remembering recently used instances (cluster/namespace) in the global selector reduces repetitive navigation. The proposed approach (localStorage-based MRU list, capped at 5-10 entries) is the standard pattern.
Implementation notes:
- Use `localStorage` with a namespaced key (e.g., `studio:recent-instances:<userId>`) to avoid conflicts
- Consider syncing recent instances across devices if Studio has user accounts
- Show a visual indicator (e.g., clock icon) to distinguish recent items from the full list
- Handle the case where a recent instance no longer exists (stale entry cleanup)
**Recommendation:** proceed — low complexity, meaningful UX improvement for multi-cluster users.
---
*Automated evaluation by github-manager-bot*
--
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: commits-unsubscribe@rocketmq.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org