ClickUp RollUps Explained: Automatic Totals from Related Tasks

Performance & Refresh Behavior

A few practical notes from real-world use:

• Rollups usually update very quickly for small sets of related tasks.
• With larger sets (hundreds of related tasks), there can be a short delay before values update.
• If a value looks “stuck”:
  • Check that the Relationship field is still active and visible in the layout.
  • Open the parent task and one of the related tasks – in some cases this seems to help “nudge” a refresh.
• Always confirm:
  • The source field (e.g., Deal Value) still exists and is the same field type you configured in the Rollup.

How to Add a Rollup (Step-by-Step)

You can add Rollups in List/Table view (as columns) or directly inside a task as a Relationship field.

1. Add a Rollup in List View

• Open the List where you want to see Rollups (e.g., Organizations, Deals, Projects).
• Make sure your Relationships are already set up.
• Click the “+” button in the column header to add a field.
• Choose Rollup.
• Configure:
  • Related to: a specific Relationship (e.g., “Deals”, “Invoices”, “Tickets”)
  • Field to roll up: e.g., Deal Value, Close Date, Time Tracked, Invoice Amount
  • Calculation: Sum, Average, Range, Count (depending on field type)
• Save. The column will populate with the calculated values.

Note: Rollup fields in List view only display in the List views you add them to. They are not Custom Fields and do not appear in task view by default.

2. Add a Rollup in Task View (as a Relationship Field)

• Open any task where you want a summary (e.g., an Organization record).
• Add a new Relationship field.
• Enable Create rollup fields to create columns from that List’s fields.
• Pick the source field and the calculation.
• Save.

Examples (Using the IT Visionists Structure)

Assuming you have Lists like:

• Organizations (clients)
• Deals (sales opportunities, linked to Organizations)
• Projects (delivery work for those clients)
• Invoices (billing, linked to Deals or Projects)
• Tickets (support/change requests, linked to Organizations/Projects)

Here’s how Rollups fit in.

1. Total Deal Value per Organization

• • Goal: See the total pipeline value per client.

• Setup:

• • Relationship: Deals → Organizations
  • On the Organizations List, add a Rollup:
    • Related to: Deals
    • Field: Deal Value (money/number)
    • Calculation: Sum
• Result: One column showing the total value of all Deals for each Organization.

2. Project Budget Portfolio per Client

• • Goal: Track total project budget for each client.

• Setup:

• • Relationship: Projects → Organizations
  • On Organizations, add a Rollup:
    • Related to: Projects
    • Field: Budget (money/number)
    • Calculation: Sum
• Result: A portfolio-style view of budget per client.

3. Support Time by Organization

• • Goal: Monitor how much support time you’re spending per client.

• Setup:

• • Relationship: Tickets → Organizations
  • On Organizations, add a Rollup:
    • Related to: Tickets
    • Field: Time Tracked
    • Calculation: Sum
• Result: A total support time figure per Organization, great for spotting high-touch clients.

4. Outstanding Invoice Amount per Deal

• • Goal: See unpaid invoice totals by Deal.

• Limitation to be aware of:

• • • Rollups can’t filter by “Status = Unpaid” internally.

• Workable approach:

• • Use either:
    • A separate Relationship for unpaid invoices only (e.g., automation moves “Unpaid” invoices into a list or relationship called “Unpaid Invoices”),
    • or a Formula field on the Invoice like Outstanding Amount that is Invoice Amount when Status is Unpaid, and 0 otherwise.
  • Roll up that Outstanding Amount field to the Deal.
• Result: A single figure per Deal showing the unpaid value.

Rollups, Dashboards, and Formula Fields

A few subtle but important boundaries:

Rollups & Dashboards

There is no dedicated “Rollup widget” on Dashboards.

Rollup values are just fields on tasks.

Rollups & Formula Fields

You can:

• Create a Formula field on a task (e.g., Remaining Budget, Outstanding Amount).
• Then Roll up that Formula field using a Rollup.

You cannot:

• Use a Rollup field inside a Formula field. Formulas don’t accept Rollups as inputs.

Note: Formula fields that use TODAY() have extra limitations: you generally can’t sort, filter, group, or use them in Dashboard Calculation cards.

Pro Tips

From implementing this in multiple workspaces:

• Structure first, Rollups second

• • • Get your Relationships right (e.g., Organizations → Deals → Projects → Invoices) before adding Rollups.

• Use Relationships over deep subtasks for reporting

• • • Subtasks only support rollups for Time Estimates and Time Tracked. For cross-List reporting or other fields, Relationships are required.

• No filters inside Rollups

• • • Plan ahead for things like “only unpaid” or “only active” by:
      • Using separate Relationships or Lists, or
      • Using Formula fields that output 0 when something shouldn’t be included.

• Normalize numeric fields

• • • Make sure “Deal Value”, “Budget”, “Invoice Amount”, etc. are consistently set up as Number/Money fields, not text.

• Check blanks first

• • If a Rollup is blank or off:
    • Confirm the Relationship actually exists.
    • Check the source field type.
    • Re-check the chosen calculation.

Final Thoughts

Rollups are where your ClickUp Relationships start paying off.

Use Relationships to define how your data is connected (Organizations, Deals, Projects, Invoices, Tickets). Then use Rollups to turn those links into live numbers and summaries you can actually make decisions from.

Once you’re comfortable with the basics, combining:

• Well-designed Relationships
• Targeted Rollups
• Formula fields for edge cases

will give you a reporting layer that replaces a surprising amount of spreadsheet work.