Skip to content

FE: UX: Hide internal topics by default #1073

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
2 tasks done
amitkrsah opened this issue May 13, 2025 · 5 comments
Open
2 tasks done

FE: UX: Hide internal topics by default #1073

amitkrsah opened this issue May 13, 2025 · 5 comments
Labels
area/topics area/ux User experiense issues good first issue Up for grabs scope/frontend Related to frontend changes status/triage/completed Automatic triage completed type/enhancement En enhancement/improvement to an already existing feature

Comments

@amitkrsah
Copy link

amitkrsah commented May 13, 2025

Issue submitter TODO list

  • I've searched for an already existing issues here
  • I'm running a supported version of the application which is listed here and the feature is not present there

Is your proposal related to a problem?

No response

Describe the feature you're interested in

Describe the bug:
When using Kafka UI, internal topics (such as __consumer_offsets, etc.) are not hidden by default. Upon logging in and navigating to the “Browse Topics” section, all topics—including internal ones—are displayed automatically. This behavior occurs even if the internal topics were previously hidden or filtered out in a prior session.

Expected behavior:
Internal topics should ideally be hidden by default, or there should be an option in the configuration or UI settings to toggle this behavior. This would help improve usability and reduce clutter for users who don’t need to view internal topics regularly.

To Reproduce:

  1. Log in to Kafka UI
  2. Navigate to the “Browse Topics” section
  3. Observe that internal topics are visible by default
  4. Manually apply a filter to hide them (if desired)

Environment:
• Kafka UI Version: v1.2.0

Additional context:
This isn’t a major bug, but more of a usability concern. Especially in environments with many topics, seeing internal ones mixed in by default makes navigation a bit harder. Having an option in the UI or config file (e.g., hideInternalTopics: true) would be a great improvement.

Describe alternatives you've considered

No response

Version you're running

v1.2.0

Additional context

No response

@amitkrsah amitkrsah added status/triage Issues pending maintainers triage type/feature A brand new feature labels May 13, 2025
@kapybro kapybro bot added area/topics status/triage/manual Manual triage in progress status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels May 13, 2025
Copy link

Hi amitkrsah! 👋

Welcome, and thank you for opening your first issue in the repo!

Please wait for triaging by our maintainers.

As development is carried out in our spare time, you can support us by sponsoring our activities or even funding the development of specific issues.
Sponsorship link

If you plan to raise a PR for this issue, please take a look at our contributing guide.

@Haarolean
Copy link
Member

This behavior occurs even if the internal topics were previously hidden

This shouldn't be the case though — your preferences are saved in browser's local storage. Unless you're in incognito, this should work. Can you check? Dev console -> application tab -> Local storage -> 'hideInternalTopics'

We'll alter the default behavior tho, makes more sense.

@Haarolean Haarolean added good first issue Up for grabs type/enhancement En enhancement/improvement to an already existing feature scope/frontend Related to frontend changes area/ux User experiense issues and removed type/feature A brand new feature status/triage/manual Manual triage in progress labels May 13, 2025
@Haarolean Haarolean changed the title Internal topics are not hidden by default when browsing topics in Kafka UI FE: UX: Hide internal topics by default May 13, 2025
@Haarolean Haarolean moved this to Todo in Up for grabs May 13, 2025
@amitkrsah
Copy link
Author

Once the preferences are set, it's saved in local storage and applicable to all clusters configured

Image

@Haarolean
Copy link
Member

Once the preferences are set, it's saved in local storage and applicable to all clusters configured

Image

yeah, so the "This behavior occurs even if the internal topics were previously hidden" part isn't valid, right?

@amitkrsah
Copy link
Author

Well, once the system is restated its reverted! Then I have to again hide it !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/topics area/ux User experiense issues good first issue Up for grabs scope/frontend Related to frontend changes status/triage/completed Automatic triage completed type/enhancement En enhancement/improvement to an already existing feature
Projects
Status: Todo
Development

No branches or pull requests

2 participants