Skip to content
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

Group By revamp for Table and Kanban Views #8203

Open
Tracked by #8202
Bonapara opened this issue Oct 30, 2024 · 0 comments
Open
Tracked by #8202

Group By revamp for Table and Kanban Views #8203

Bonapara opened this issue Oct 30, 2024 · 0 comments
Assignees
Labels
prio: low scope: front Issues that are affecting the frontend side only size: long type: design improvement

Comments

@Bonapara
Copy link
Member

Bonapara commented Oct 30, 2024

Current Behavior

We can use the group-by function on kanbans, but not on tables yet.

Desired Behavior

We want to unify the group-by behavior on both table and kanban views. Therefore, we aim to rename the kanban stages setting to group by in the kanban options menu.

Options menu "root" level

CleanShot 2024-10-30 at 14 53 59

Display the chosen Select field name

Group by menu

CleanShot 2024-10-30 at 14 53 28

Group by Options

CleanShot 2024-10-30 at 14 57 39

  • Allows to choose which select field to use for the group by. None should only available for table views (as you can't create a Kanban view without group by).
  • Create Select Field should redirect to /settings/objects/xxx/new-field/configure?fieldType=SELECT

image

This is what should be shown when no select field is available on a table view

Sort Options

CleanShot 2024-10-30 at 15 03 05

Hide Empty Groups

CleanShot 2024-10-30 at 15 05 02

Hide columns that don't contain at least one card.

Visible groups

Disable the grips if Alphabetical or Reverse-Alphabetical is selected

CleanShot 2024-10-30 at 15 05 11

Customize which fields are displayed and in what order.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prio: low scope: front Issues that are affecting the frontend side only size: long type: design improvement
Projects
Status: 🔖 Planned
Development

No branches or pull requests

2 participants