apache / apache/rocketmq-dashboard
[Studio][Feature] Save reusable Message Explorer query presets
- Dominant language
- Java
- Stars
- 1.4k
- Forks
- 683
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 58
Description
## Problem
Message Explorer records completed executions in server-side history, but operators cannot name and reuse a query before running it. Repeated investigations therefore require re-entering the same instance-scoped Topic, Message Key or Message ID criteria and time range. Execution history is not a substitute because it is immutable, result-oriented and may be removed by retention cleanup.
The current rocketmq-studio branch has no saved-query model or UI. Searches across open and closed repository Issues and PRs for saved message query, query preset, saved search and bookmark found no matching work as of 2026-09-04.
## Proposed behavior
- Save a complete Topic, Message Key, or Message ID query under an operator-provided name.
- Scope presets to the selected RocketMQ instance so identical resource names cannot cross instance boundaries.
- Search, apply, rename and delete presets from Message Explorer.
- Persist a bounded browser-local collection and tolerate unavailable or corrupted storage.
- Synchronize updates made in another browser tab.
- Provide Chinese and English labels and focused regression coverage.
## Acceptance criteria
- Incomplete criteria cannot be saved.
- Duplicate names are rejected within one instance but may be reused by another instance.
- At most 50 valid presets are retained, newest first.
- Removed instances do not expose another instances presets.
- Applying a preset updates the form without issuing a request until the operator chooses Query.
- Storage failures are visible and never report a false success.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the Message Explorer entry point and inspect the existing query form and execution-history behavior, especially instance scoping. Then trace browser-local storage and cross-tab updates; done means the acceptance criteria hold, including validation, 50-item retention, isolation, no request on apply, visible storage failures, bilingual labels, and focused regression coverage.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100