---
title: "Column data aggregation methods"
canonical: "https://support.appfire.com/space/DLP/2211583266/Column%20data%20aggregation%20methods"
format: markdown
---
> Macro (aura-html)
## Data aggregation in the column view
You can aggregate data on several different columns that display numeric data. Depending on the data field the column represents, not all methods are available. Aggregation methods roll up data from children and display the result on the parent.
You can aggregate all task types, including basic tasks and milestones.
> ✅ **Aggregation can be adjusted directly in the module views**
> ✅
> ✅ - Those changes are temporary and reversible (until you save them and update the view).
> ✅ - Temporary changes made to your current view affect only you (other users don’t see them).
> ✅ - Available options differ depending on the field.
> ✅
> ✅ 
### None
The **None** aggregation method means that no aggregation is applied to the data in that specific column. This setting essentially disables any type of summarization or consolidation of the data, and it leaves the raw, individual data values visible without any kind of calculation or combination.
When to use aggregation **None**:
- When you don't need to aggregate data but rather need to track individual values.
- When you want to maintain visibility into all individual elements.
In the example below, the **Duration Working Days** column displays the duration of the “Location search” task as is, based on its start and end dates.
### Minimum
The **Minimum** aggregation method** **shows the smallest value in a parent column when multiple items or tasks are under consideration. This aggregation type helps to highlight the lowest or least significant value across a group of tasks, issues, or other data points.
When to use aggregation **Minimum**:
- When you want to find the smallest value in a set of data, such as the shortest time, the least amount of work, or the earliest deadline.
- It is useful for highlighting tasks that may require the least effort or that need to be completed first (in terms of due date or duration).
In the example below, the **Duration Working Days** column displays the duration of the “Location search” task as 0 days based on the milestone “Location found” (milestones have no duration). If we were to remove the milestone from the structure, the value would switch to 21 (the days it will take to complete the task “Survey and footprint the house”).
### Maximum
The **Maximum** aggregation method shows the largest value in a column when there are multiple items, tasks, or issues in that column. This aggregation type helps you identify the highest or most significant value across a group of data points.
When to use aggregation **Maximum**:
- When you have tasks with different time or effort estimates, applying **Maximum** aggregation will show the task with the highest estimated time or effort.
- If you're tracking task progress, the **Maximum** aggregation can display the highest progress percentage, helping you see the most completed task.
- In cases where you are tracking deadlines, applying the **Maximum** aggregation will display the latest due date, indicating the task that has the farthest deadline.
In the example below, the **Duration Working Days** column displays the duration of the “Location search” task as 33 based on the task “Select a desirable place for the model house.”
### Sum
The **Sum** aggregation method adds** **up all the values in a column. This aggregation type lets you quickly calculate the total of a set of values for multiple tasks and their parent.
When to use aggregation **Sum**:
- When you want to calculate the total of any numeric values in a column, such as total effort, time spent, cost, duration, completion, or story points.
- It is particularly useful for reporting on cumulative metrics across multiple tasks or issues.
In the example below, the **Duration Working Days** column displays the duration of the “Location search” task as 169 based on the duration of the parent and all the tasks under that parent.
### Sum, without parent
The **Sum, without parent** aggregation method is a variation of the **Sum** aggregation. It adds the values of the child tasks or issues but excludes the parent task from the calculation.
When to use aggregation **Sum, without parent**:
- When you are focused on the total of child tasks (for example, total effort, cost, or time) but do not want to include the parent's aggregated values.
- This aggregation method is helpful for granular insights into the lower-level work, without distorting the overall numbers with higher-level aggregations.
In the example below, the **Duration Working Days** column displays the duration of the “Location search” task as 85 based on the duration of all the tasks under that parent.
### Average
The **Average** aggregation method calculates the average (mean) value of a specific column across multiple tasks or issues. Instead of showing the sum of the values, it provides the average value for a set of tasks and their parent.
When to use aggregation **Average**:
- When you want to understand the average completion level, effort, or cost for tasks without focusing on extreme values.
- When you need a more balanced view of metrics by smoothing out any large or small values that might skew the results.
In the example below, the **Duration Working Days** column displays the duration of the “Location search” task as 33.8 based on the duration of all the tasks and their parent.
### Average, without parent
The **Average, without parent** aggregation method is a variation of the **Average** aggregation. It calculates the average value of child tasks or issues while excluding any parent tasks from the calculation.
This type of aggregation lets you focus on the average of the child tasks without considering the parent task's value, ensuring that only the individual task data is included.
When to use aggregation **Average, without parent**:
- When you want to calculate the average value of child tasks only and exclude the parent task's aggregated value from affecting the result.
In the example below, the **Duration Working Days** column displays the duration of the “Location search” task as 21.25 based on the duration of all the tasks under that parent.
### Status categories in %
The **Status categories %** aggregation method is a specific aggregation type used to represent the distribution of tasks and their parent based on their status categories as percentages.
This type of aggregation shows how tasks are distributed across different status categories, such as **To Do**,** In Progress**,** Completed**, or any custom status categories defined in your project.
The result is presented as a percentage of tasks and the parent that falls into each status category, displayed in a **Lozenge** format. The data is shown even if you do not have the **Status** column added to your current view.
When to use aggregation **Status categories %**:
- This aggregation is ideal when you want to quickly see how tasks and a parent are progressing across different status categories.
- When you want to identify where tasks are stalled (for example, if a large percentage of items are still in the "To Do" category) and take action to move them forward.
- When you want to see how much work is completed, how much is in progress, and how much is still pending.
In the example below, the **Duration Working Days** column displays each status category and the percentage of tasks (including the parent) that fall into each category. Note that the data is aggregated by the status only; the duration of the task is irrelevant.
### Children status categories
The **Children status categories** aggregation method is a specific aggregation type used to represent the distribution of tasks based on:
- status categories of the child tasks
- value under the specific column.
This aggregation type lets you see the distribution of child task statuses (for example, **To Do**, **In Progress**, **Completed**) without being influenced by the parent task status and value.
The result is presented as a sum of values of tasks that fall into each status category, displayed in a **Lozenge** format. The data is shown even if you do not have the **Status** column added to your current view.
When to use aggregation **Children** **status categories**:
- When you want to see the number of days, cost, story points, etc., that have remained in each category.
In the example below, the **Duration Working Days** column displays the total number of working days from all tasks and groups them into their status-based categories.
### Children status categories in %
The **Children status categories %** aggregation method is a specific aggregation type used to represent the distribution of tasks excluding their parent based on their status categories as percentages.
This type of aggregation shows how tasks are distributed across different status categories, such as **To Do**,** In Progress**,** Completed**, or any custom status categories defined in your project.
The result is presented as a percentage of tasks that fall into each status category, displayed in a **Lozenge** format. The data is shown even if you do not have the **Status** column added to your current view.
When to use aggregation **Children** **status categories**:
- When you need a percentage-based overview of how child tasks are spread across different statuses.
- When managing a large project with multiple tasks and subtasks, this aggregation gives a quick view of the number of child tasks in each status, which helps to track progress.
- This aggregation type helps you identify if a high percentage of child tasks are stuck in a particular status, like "To Do" or "In Progress", which may indicate delays or bottlenecks.
In the example below, the **Duration Working Days** column displays each status category and the percentage of tasks (excluding the parent) that fall into each category. Note that the data is aggregated by status only; the duration of the task is irrelevant.
