kafbat/kafka-ui

Consumer search criteria not cleared/used when navigating to another consumer

Open

#1,221 opened on Jul 25, 2025

View on GitHubContributor guide
 (5 comments) (0 reactions) (1 assignee)TypeScript (363 forks)auto 404
area/uxgood first issuescope/frontendstatus/triage/completedtype/bug

Repository metrics

Stars
 (2,554 stars)
PR merge metrics
 (PR metrics pending)

Description

Issue submitter TODO list

  • I've looked up my issue in FAQ
  • I've searched for an already existing issues here
  • I've tried running main-labeled docker image and the issue still persists there
  • I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

If I go the consumer tab, enter in anything to the search field, the results are filtered. If I then immediately go to another clusters consumer tab, the search term is still present but the results are not filtered.

Expected behavior

I'd think that the search term should clear or the results should be filtered, the latter would be my preference.

Your installation details

Docker Version 8b5494b

Steps to reproduce

See above in the description.

Screenshots

No response

Logs

No response

Additional context

No response

Contributor guide

Research direction
Trace the lifecycle of the consumer search state. Determine where the search term is stored (e.g., local component state, Redux store, URL query) and why it persists when switching clusters. Inspect the Consumer component and the navigation actions on the cluster page.
Tech stack
typescript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65