yuluo-yx opened a new issue, #3057:
URL: https://github.com/apache/rocketmq-dashboard/issues/3057

   ## 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.


-- 
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]

Reply via email to