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

Column Management Modal Improvements (Grouping, Popovers, and State-based Actions)

Open
#869 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
frontend

Research direction

Start by reviewing the linked Column Management modal demo, prototype, and Figma design, then compare the proposed grouping, group-title popovers, and conditional Restore behavior with the current component. Done means the three enhancements are implemented and their behavior matches the agreed design; the Jira issue PF-3516 may provide additional requirements.

Written by the indexing model from the issue text.

Description

While working on a feature requiring complex table customization, I’ve been exploring some potential enhancements to the Column Management modal:

Proposed Enhancements:

  • Expandable Column Groups: Add support for grouping related columns within the modal. This is especially useful for tables with many columns, allowing users to expand/collapse sections to find what they need more efficiently.
  • Popovers on Group Titles: Allow for informational popovers on group headings to provide additional context or descriptions for specific categories of data.
  • Conditional "Restore" State: Disable the Restore default columns action if the user has not made any changes from the default state. This reduces visual noise and clarifies when a customization has actually occurred.

Supporting Documentation:


Jira Issue: PF-3516

Dominant language
TypeScript
Stars
10
Forks
40
Avg merge
3d 22h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

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 patternfly/react-component-groups

All issues in patternfly/react-component-groups

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.