---
title: "Column view (Overview module)"
canonical: "https://support.appfire.com/space/DLP/2212235726/Column%20view%20(Overview%20module)"
format: markdown
---
> Macro (aura-html)
Get the most information out of your data. The data visible in the columns of the Overview module provides high-level insight into your data. Modify the view to best meet your needs.
## Box vs task data columns
> Macro (excerpt)
>
> **Box-associated columns** show data associated with Boxes (not tasks) and are visible only in the Overview module.
>
> **Task-associated columns **show data aggregation based on individual tasks (inline editing won't be possible in the Overview module). Those columns are marked with "tasks" in the name:
See the list of task-associated columns
- Actual cost (Tasks)
- Baseline End Date (Tasks)
- Baseline Start Date (Tasks)
- End Date (Tasks)
- Estimated Cost (Tasks)
- Original Estimate (Tasks)
- Progress (Tasks)
- Remaining Estimate (Tasks)
- Start Date (Tasks)
- Story Points (Tasks)
- Time Spent (Tasks)
- Time Tracking (Tasks)
Task information has to be edited in a module (such as Gantt - the value of the "actual cost" column associated with a particular task can be adjusted). The word "tasks" won't appear in the column name in the modules because data in the modules is associated with tasks only (not Boxes):
> ℹ️ Those columns are based on [built-in fields](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211647594).
> ℹ️
> ℹ️ Task value fields are available for all tasks (including [basic tasks](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211352313)).
## Inline editing of box attributes
You can use [inline editing](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211578149) to edit values directly in the Overview module.
See the screenshot
### Limitations
Not all box attributes are editable. For **Closed** and **Archived** boxes, box attributes can't be edited.
## Aggregated box status
Aggregated box status is calculated for all Boxes.
Status-based report is based on the scope of all sub-boxes. It shows issue distribution in different Jira status categories for each upper-level Box:
- To Do - grey color
- In Progress - blue color
- Done - green color
If a closed box does not have any aggregation yet, it is calculated once. Aggregations for all closed boxes that already have an aggregation are not calculated.
## Aggregated time-tracking report
Aggregated Box status is calculated for all Boxes.
Time-tracking report based on the scope of all sub-Boxes showing issue progress. The formula used is: 1-(Remaining estimate/Original estimate)*100%
If a closed box does not have any aggregation yet, it is calculated once. Aggregations for all Closed Boxes that already have an aggregation are not calculated.
## Capacity column
You can have a quick overview of the team members' capacity in a given box.
The calculation is done for:
- team members only
- for the box period only
Manual changes made on Board module > Capacity planning are **not** included in the calculation
### Customization** **
You can display data in the following formats:
- Pretty (combines different units e.g., 4w 23d)
- Days
- Hours
- Decimal
### Limitations
- It is **not possible** to convert the capacity in **hours to Story Points** in this column.
- it is **not possible** to **change the aggregation** method in the column (always sum of capacity from a given Box only).
> Macro (anchor)
## Cost columns
The following columns can be added to the Overview module view:
- **Information associated with boxes → **values are associated with boxes only. They don't depend on task information.
- Budget
- Estimated Cost
- Actual Cost
- **Information associated with tasks →** values are associated with tasks in a box.
- Estimated Cost (Tasks)
- Actual Cost (Tasks)
### Aggregation
Configure the table so that the app rolls up the value in the Box hierarchy (choose aggregation).
Columns can be customized, resulting in different aggregation of data:
- None
- Minimum
- Maximum
- Sum
- Sum, without a parent
- Average
- Average, without a parent
- Status in categories in %
- Children status categories
- Children's status categories in %
See the example
In the example below, the value is based on the actual cost of tasks in boxes.
**Box vs task data columns**
> Macro (excerpt-include)
Corresponding columns:
| **Overview module** | **Gantt** | **Scope** | **Board** |
| --- | --- | --- | --- |
| **Actual Cost (Tasks)** | Actual cost | Actual cost | Actual cost |
| **Estimated Cost (Tasks)** | Estimated Cost | Estimated Cost | Estimated Cost |
| **Budget** | N/A | N/A | N/A |
| **Actual Cost** | N/A | N/A | N/A |
| **Estimated Cost** | N/A | N/A | N/A |
Adjust the column view. Then, use inline editing to adjust task information.
See the screenshots
Gantt module:
Scope module:
Board module:
If you want to change the details of already planned tasks (tasks shown as cards assigned to sub-boxes on the left), change the filtering options in the Backlog to display all tasks.
See the screenshot
> ℹ️ Those columns are based on [built-in fields](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211647594).
> ℹ️
> ℹ️ Fields are available for all tasks (including [basic tasks](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211352313)).
**Field mapping**
**Actual cost** and **Estimated cost** fields can be mapped to a Jira field.
When fields are set to "Not Synchronized" the values are stored in the app only.
## Story points and Progress fields
Additional task calculated fields:
- Story Points
- Progress
Details about the box resulting from its box type settings are known to an operational user (for example, Box Editor, Box Admin) as they are visible only in [box type configuration](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2212266090), but those settings might affect your work with the boxes.
### Customization
## Box details
Any user can check details about the box resulting from its box type settings in the Overview module. Those settings might affect the User's work with the Boxes and are configured in the **Administration** > **[Box types](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2212266003)** section.
The following box information columns are available on the Overview module:
- [Period mode](https://appfire.atlassian.net/wiki/pages/createpage.action?spaceKey=dlpdraft&title=NEW%20Scheduling%20mode%20field&linkCreation=true&fromPageId=2024287383)
- Sequentiality
- Created date
- [Scope type](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211126618)
The scope type column shows the actual scope type of a box** **(which is set during Box creation and cannot be changed later).
See the use case
Use case:
- A Program Increment was created. At the time, the "Program Increment" box type was set to "Sub"
- An admin changed the scope of the Program Increment box type → now, the Program Increment box type is set to "Own."” This change won't affect existing "Program Increment" boxes.
- In the Overview column, you can see the actual scope type of a box (even if scope type settings have been changed for a box type)
## Archived boxes
You can also add an **Archived **column to the view. [Archived boxes](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211939473) are only visible in the following **View** settings.
The data visible in the columns of the Overview module provides you with high-level insight into your data. Modify the view to best meet your needs.
> Macro (anchor)
## Closed date column
The **closed date** column allows you to compare the End date to the date of actual closing (changing the status to "Closed"). The user can add a 'Closed Date' column to the Overview module under the "Manage column."
The column is not inline-editable and has the same aggregations as other Date types, that is, None, Minimum, and Maximum.
## Inactive for column
Add the **Inactive for** column to see when the Box has been used for the last time.
This information is useful when:
- [auto-archiving of boxes](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211939473) is active
- you want to activate the auto-archiving of boxes - you can see which boxes will meet the criteria and be archived
You can easily [filter data](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211646060) using the **Inactive for** column.
