# Multi-level groups and support more field types for grouping

**URL:** <https://community.fibery.io/t/multi-level-groups-and-support-more-field-types-for-grouping/8215>\
**Category:** Ideas & Features\
**Created:** [February 4, 2025, 7:30pm UTC](https://community.fibery.io/t/multi-level-groups-and-support-more-field-types-for-grouping/8215 "2025-02-04T19:30:48Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![MrLY](https://avatars.discourse-cdn.com/v4/letter/m/f07891/32.png) [@MrLY](https://community.fibery.io/u/MrLY)\
**Post date:** [February 4, 2025, 7:30pm UTC](https://community.fibery.io/t/multi-level-groups-and-support-more-field-types-for-grouping/8215/1 "2025-02-04T19:30:48Z")

</div>

Hello!

I think it would be great if we could apply more than just 1 level of grouping to a table/list but more importantly support to group by formulas and date fields would be really useful!

For example I am tracking time spent on projects and it would be great to group the time entries by the month and see the total time spent each month.

And to use the same example for the multiple levels of grouping, I could group by year, month, week to get even more granular summaries on the timesheets.

Of course I assume this information could be obtained via reports/charts but I am on the free plan at the moment and I imagine there would be a lot of use cases for these features.

---

<div class="post-metadata">

**Author:** ![Michael\_Ichter](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/michael_ichter/32/9931_2.png) [@Michael\_Ichter](https://community.fibery.io/u/Michael_Ichter)\
**Post date:** [February 7, 2025, 7:54am UTC](https://community.fibery.io/t/multi-level-groups-and-support-more-field-types-for-grouping/8215/2 "2025-02-07T07:54:35Z")

</div>

I’d also like multi-level grouping. For our task database, it would look nice if we could group by the state field and then also group by our Parent task (recursive) relation. It would look more organized then what we’re doing now: group by parent task and then sorting by state.

---

<div class="post-metadata">

**Author:** ![Alex\_Rublev](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/alex_rublev/32/10881_2.png) [@Alex\_Rublev](https://community.fibery.io/u/Alex_Rublev)\
**Post date:** [February 27, 2025, 2:14pm UTC](https://community.fibery.io/t/multi-level-groups-and-support-more-field-types-for-grouping/8215/3 "2025-02-27T14:14:47Z")

</div>

Multi-level groups is something we’d like to have too 👍

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [February 27, 2025, 4:01pm UTC](https://community.fibery.io/t/multi-level-groups-and-support-more-field-types-for-grouping/8215/4 "2025-02-27T16:01:50Z")

</div>

But you can create quite deep hierarchies with lists/tables already, could you clarify what do you need here?

---

<div class="post-metadata">

**Author:** ![Alex\_Rublev](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/alex_rublev/32/10881_2.png) [@Alex\_Rublev](https://community.fibery.io/u/Alex_Rublev)\
**Post date:** [February 27, 2025, 4:14pm UTC](https://community.fibery.io/t/multi-level-groups-and-support-more-field-types-for-grouping/8215/5 "2025-02-27T16:14:40Z")

</div>

For example: I can’t group by Client → Project _(Because Work Unit doesn’t have relation to Project, it gets Project from Order)_

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/efaf5fb7dc3e98e3b09cd21087d1b2f392f05d55.png)

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [February 27, 2025, 4:17pm UTC](https://community.fibery.io/t/multi-level-groups-and-support-more-field-types-for-grouping/8215/6 "2025-02-27T16:17:05Z")

</div>

Can you share relations for these databases?

---

<div class="post-metadata">

**Author:** ![MrLY](https://avatars.discourse-cdn.com/v4/letter/m/f07891/32.png) [@MrLY](https://community.fibery.io/u/MrLY)\
**Post date:** [February 27, 2025, 4:20pm UTC](https://community.fibery.io/t/multi-level-groups-and-support-more-field-types-for-grouping/8215/7 "2025-02-27T16:20:08Z")

</div>

The deep hierarchies work fine if you have relationships, but there are instances where you may wish to group entities by multiple fields that aren’t from a relationship, e.g. grouping tasks by priority and then status

---

<div class="post-metadata">

**Author:** ![Alex\_Rublev](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/alex_rublev/32/10881_2.png) [@Alex\_Rublev](https://community.fibery.io/u/Alex_Rublev)\
**Post date:** [February 28, 2025, 6:12am UTC](https://community.fibery.io/t/multi-level-groups-and-support-more-field-types-for-grouping/8215/8 "2025-02-28T06:12:24Z")

</div>

Overall, MrLY explains everything correctly. If the entities have direct relations, then yes – the grouping works to any desired depth. However, if they are connected through formulas or lookups, this functionality is lost because there’s no relationship tree.

Currently, I’m directly linking everything, using auto-linking, which requires me to implement workarounds.

`For example, initially, it was like this:`  
**Order** gets **Client** from **Project** via **Lookup** – nested grouping was not possible.

`Now, I do it this way:`  
**Order** gets **Client’s Public ID** from **Project** to **Client PID field**.  
**Order** is auto-linked to **Client** using the **Client PID field**.

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [May 5, 2025, 5:01pm UTC](https://community.fibery.io/t/multi-level-groups-and-support-more-field-types-for-grouping/8215/9 "2025-05-05T17:01:38Z")

</div>

Not being able to group entities by their date, relative to today is a real pain.  
There’s no easy way to see tasks or events for “Tomorrow” and “Next Week”

---

<div class="post-metadata">

**Author:** ![kzndotsh](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/kzndotsh/32/12092_2.png) [@kzndotsh](https://community.fibery.io/u/kzndotsh)\
**Post date:** [June 26, 2025, 3:35pm UTC](https://community.fibery.io/t/multi-level-groups-and-support-more-field-types-for-grouping/8215/10 "2025-06-26T15:35:57Z")

</div>

Multi level grouping is essential for maximizing an application like this. Airtable does this very nicely.

---

<div class="post-metadata">

**Author:** ![Jonathan](https://avatars.discourse-cdn.com/v4/letter/j/aeb1de/32.png) [@Jonathan](https://community.fibery.io/u/Jonathan)\
**Post date:** [September 5, 2025, 12:39am UTC](https://community.fibery.io/t/multi-level-groups-and-support-more-field-types-for-grouping/8215/11 "2025-09-05T00:39:14Z")

</div>

Add another request for multi-level grouping. Let’s say you have a hierarchy of tasks grouped by parent task (recursive). But you also want to group by some categorical label, you can’t, because you’ve already “used up” your one level of grouping just to show the task hierarchy. In some of Fibery’s examples, they use multiple databases to establish a hierarchy, and then group by some categorical label, so they are aware of the desired behavior. Sometimes there’s also hierarchy within a single database (not only across different databases), and you’d also want to see the hierarchy within a single database without losing the ability to group by labels, too.

@

---

<div class="post-metadata">

**Author:** ![matthew](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matthew/32/15180_2.png) [@matthew](https://community.fibery.io/u/matthew)\
**Post date:** [October 8, 2026, 5:11pm UTC](https://community.fibery.io/t/multi-level-groups-and-support-more-field-types-for-grouping/8215/12 "2026-10-08T17:11:29Z")

</div>

Loving Fibery so far! As a recent convert coming from Airtable and Google Sheets, it would be incredibly useful to have grouping by more than one attribute. Even if it was just for structured items like drop-down Single Select Fields or Relation fields.

Also, the ability to see basic summaries in the columns for each of the grouped rows so if you want to breakdown (instead of just a column total at the bottom) into smaller subtotals.
