# Noloco roll-ups: Count specific statuses from linked records

**URL:** <https://community.noloco.io/t/noloco-roll-ups-count-specific-statuses-from-linked-records/469>\
**Category:** Feature Requests\
**Created:** [March 29, 2024, 9:23am UTC](https://community.noloco.io/t/noloco-roll-ups-count-specific-statuses-from-linked-records/469 "2024-03-29T09:23:36Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![JCW](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/jcw/32/173_2.png) [@JCW](https://community.noloco.io/u/JCW)\
**Post date:** [March 29, 2024, 9:23am UTC](https://community.noloco.io/t/noloco-roll-ups-count-specific-statuses-from-linked-records/469/1 "2024-03-29T09:23:36Z")

</div>

The ask: In a main table I would like to monitor the progress of linked tasks. This could be a project with subtasks or an order where I want to see in the headline of the main element how many subitems are still in which status.

Now with the help of a rollup field, at the moment I can count the total elements of subtasks which is fine. But I cannot count the elements of linked records in a specific status i.e. “in progress” or “done”. If I could, I could report on that in the main task / project.

Use cases here are imaginable in projects, tasks, orders, and numerous other areas.

---

<div class="post-metadata">

**Author:** ![buildwithjoel](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/buildwithjoel/32/1537_2.png) [@buildwithjoel](https://community.noloco.io/u/buildwithjoel)\
**Post date:** [March 29, 2024, 9:00pm UTC](https://community.noloco.io/t/noloco-roll-ups-count-specific-statuses-from-linked-records/469/2 "2024-03-29T21:00:34Z")

</div>

Essentially what this sounds like is a “filter” step for rollup field configurations. That would allow you to filter the subtasks that are rolled up by a desired condition (e.g. their status).

If so, I definitely agree. You can see this illustrated in Airtable’s rollup fields:  
 ![Screenshot 2024-03-29 at 4.59.23 PM](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/1X/fc5b7965e8a7612a8537156d6e69bae549076777.png)

---

<div class="post-metadata">

**Author:** ![JCW](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/jcw/32/173_2.png) [@JCW](https://community.noloco.io/u/JCW)\
**Post date:** [March 29, 2024, 9:29pm UTC](https://community.noloco.io/t/noloco-roll-ups-count-specific-statuses-from-linked-records/469/3 "2024-03-29T21:29:30Z")

</div>

Yes, this is what I mean. In airtable this is available. Would be fantastic to have this in noloco tables as well.

---

<div class="post-metadata">

**Author:** ![Tobias](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/tobias/32/252_2.png) [@Tobias](https://community.noloco.io/u/Tobias)\
**Post date:** [April 1, 2024, 7:24am UTC](https://community.noloco.io/t/noloco-roll-ups-count-specific-statuses-from-linked-records/469/4 "2024-04-01T07:24:21Z")

</div>

Would be really helpful as we are wanting to use local Noloco fields more and more in the future.

---

<div class="post-metadata">

**Author:** ![MikeMash](https://avatars.discourse-cdn.com/v4/letter/m/2acd7d/32.png) [@MikeMash](https://community.noloco.io/u/MikeMash)\
**Post date:** [April 3, 2024, 9:43pm UTC](https://community.noloco.io/t/noloco-roll-ups-count-specific-statuses-from-linked-records/469/5 "2024-04-03T21:43:58Z")

</div>

Definitely need this. What can I use currently as a work around if say I had a record that can be either “available” or “not available” and I need to count all of the “available” and use that number in a workflow?

---

<div class="post-metadata">

**Author:** ![Offbase](https://avatars.discourse-cdn.com/v4/letter/o/97f17d/32.png) [@Offbase](https://community.noloco.io/u/Offbase)\
**Post date:** [April 5, 2024, 4:17am UTC](https://community.noloco.io/t/noloco-roll-ups-count-specific-statuses-from-linked-records/469/6 "2024-04-05T04:17:06Z")

</div>

Currently do filters like this I create additional fields. In your case I would create 2 more fields available and “not available” either as boolean or text fields, and then count on true values.

---

<div class="post-metadata">

**Author:** ![JCW](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/jcw/32/173_2.png) [@JCW](https://community.noloco.io/u/JCW)\
**Post date:** [June 19, 2024, 3:35pm UTC](https://community.noloco.io/t/noloco-roll-ups-count-specific-statuses-from-linked-records/469/7 "2024-06-19T15:35:14Z")

</div>

@darragh This request is getting more relevant as rollups in airtable take some time before the changes come back to noloco from time to time. Definitely got some supporters 🙂 and is a solid request with valid usecases. Wondered if this is on the roadmap in the near future.

---

<div class="post-metadata">

**Author:** ![EthosLuke](https://avatars.discourse-cdn.com/v4/letter/e/46a35a/32.png) [@EthosLuke](https://community.noloco.io/u/EthosLuke)\
**Post date:** [January 23, 2025, 3:22pm UTC](https://community.noloco.io/t/noloco-roll-ups-count-specific-statuses-from-linked-records/469/8 "2025-01-23T15:22:55Z")

</div>

Giving this a bump as it’s still a much needed feature, especially if you’re trying to use Noloco tables instead of 3rd parties such as Airtable.

---

<div class="post-metadata">

**Author:** ![Amt718](https://avatars.discourse-cdn.com/v4/letter/a/74df32/32.png) [@Amt718](https://community.noloco.io/u/Amt718)\
**Post date:** [February 23, 2025, 3:31pm UTC](https://community.noloco.io/t/noloco-roll-ups-count-specific-statuses-from-linked-records/469/9 "2025-02-23T15:31:10Z")

</div>

+1 for this request. This would be a very helpful feature.

---

<div class="post-metadata">

**Author:** ![KrystalVisionCoach](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/krystalvisioncoach/32/1350_2.png) [@KrystalVisionCoach](https://community.noloco.io/u/KrystalVisionCoach)\
**Post date:** [April 29, 2025, 9:00am UTC](https://community.noloco.io/t/noloco-roll-ups-count-specific-statuses-from-linked-records/469/10 "2025-04-29T09:00:52Z")

</div>

This should have gone without saying… I was shocked to find that this was not actually possible without workarounds. This should be at the top of the roadmap as this is basic functionality that should be expected of any relational database app.

---

<div class="post-metadata">

**Author:** ![lukebranford](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/lukebranford/32/32_2.png) [@lukebranford](https://community.noloco.io/u/lukebranford)\
**Post date:** [April 30, 2025, 12:29pm UTC](https://community.noloco.io/t/noloco-roll-ups-count-specific-statuses-from-linked-records/469/11 "2025-04-30T12:29:06Z")

</div>

Surprised I’ve not +1 this before, always end up using workarounds! So +1 😉

---

<div class="post-metadata">

**Author:** ![fluxomate](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/fluxomate/32/1288_2.png) [@fluxomate](https://community.noloco.io/u/fluxomate)\
**Post date:** [May 5, 2025, 7:03am UTC](https://community.noloco.io/t/noloco-roll-ups-count-specific-statuses-from-linked-records/469/12 "2025-05-05T07:03:56Z")

</div>

If you want a workaround in the Linked database (linkedsub-tasks I assume), set up a formula field for each of the status options  
e.g If Status = Complete count 1 if else 0  
if Status = Backlog count 1 if else 0  
if Status = In Progress count 1 if else 0

Then you can individually use the roll-up function in the other database (the main tasks, I assume) for each of the individual formulas.  
From there you can also use those roll-ups in formulas to calculate %  
E.g % of tasks that are Complete = Complete Count / (Backlog + Progress + Complete count)

A bit annoying because you need to set-up each individual formula but if I understood your request correctly, this could be a potential workaround.

---

<div class="post-metadata">

**Author:** ![JCW](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/jcw/32/173_2.png) [@JCW](https://community.noloco.io/u/JCW)\
**Post date:** [August 12, 2025, 7:48pm UTC](https://community.noloco.io/t/noloco-roll-ups-count-specific-statuses-from-linked-records/469/13 "2025-08-12T19:48:15Z")

</div>

Yes this is a workaround I use but it is extremely time consuming when working with Noloco DB. Bumping this as a gentle reminder - still missing this feature a lot especially if there are more options / conditions to be checked 😉
