Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug] System alert time picker no longer applies start-only or end-only filters

Closed Beginner friendly
  • Is something wrong?
#6,636 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
nodejs
Domain
frontend

Research direction

Start at the system alert time picker, where the RangePicker is rendered, and check why a start-only or end-only selection is not committed without allowEmpty. Then confirm how the picker values are passed to the alert-list service and to export. Run the existing Vitest/jsdom page tests: the bounded-range test should keep passing, and new single-boundary cases should send only from or only to. Done when both single-boundary cases pass and the existing 21 tests still pass.

Written by the indexing model from the issue text.

Description

Before Creating the Bug Report
  • Searched existing issues and pull requests; no equivalent open-ended system-alert filter fix found.
  • This concerns RocketMQ Studio in this repository.
  • Reproduced on the current rocketmq-studio revision.
Studio Version

rocketmq-studio at e2f815fba774a1e399bf9bb3709246edca1a436d (includes #6633).

Runtime Environment

Ubuntu 24.04 ECS, Node.js 20.20.2, Vitest/jsdom, Asia/Shanghai. The actual RangePicker is rendered; only the service is mocked.

Connected RocketMQ Cluster

Not needed to reproduce this frontend request-construction defect.

Describe the Bug

#6633 replaced two independent datetime inputs with a RangePicker. Without allowEmpty, a start-only or end-only selection is not committed, so the page keeps making an unrestricted time query. Previously the inputs could set either endpoint independently, and the backend still accepts from/to independently.

Steps to Reproduce
  1. Open system alerts and enter only the start time (or only the end time).
  2. Confirm the date and leave the picker.
  3. Observe that the alert-list request still has no corresponding time boundary.
Expected Behavior

Start-only filtering submits from with no to; end-only filtering submits to with no from, using the existing local-to-UTC conversion. A bounded range continues to work.

Actual Behavior

Both single-boundary regressions fail on the current component. The existing bounded-range test passes. An isolated prototype enabling allowEmpty passes both regressions and all 23 page tests (21 existing plus 2 research cases).

Additional Context

The minimal fix preserves the single RangePicker layout and existing API, conversion, pagination reset and export query handling. Regressions should exercise the picker and service arguments, including export using each single boundary. No new UI text is needed.

Are You Willing to Submit a Pull Request?
  • Yes.
Dominant language
Java
Stars
1.4k
Forks
709
Avg merge
2d 5h
Merged PRs (30d)
157

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/rocketmq-dashboard

All issues in apache/rocketmq-dashboard

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.