---
title: "Column View"
canonical: "https://support.appfire.com/space/DLP/298288087/Column%20View"
format: markdown
---
> Macro (aura-html)
> Macro (toc)
## Introduction
Get the most information out of your data. Data visible in the columns of the Overview module provides you with high-level insight into your data. Modify the view to make sure it best meets your needs.
## Box vs task data columns
> Macro (excerpt)
>
> **Box-associated columns** show data associated with Boxes (not tasks) and are visible in the Overview module only.
>
> **Task-associated columns **show the aggregation of data 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/pages/createpage.action?spaceKey=dlp&title=Concept%20of%20a%20field%20%28r%29&linkCreation=true&fromPageId=298288087).
> ℹ️
> ℹ️ Task value fields are available for all tasks (including [basic tasks](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297702042)).
## Inline editing of box attributes
You can use [inline editing](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297963003) to edit values directly in the Overview module.
See the screenshot
**Limitations**
Not all box attributes are editable. **Closed** and **Archived** boxes - box attributes can't be edited.
## Aggregated box status
Aggregated box status is calculated for all Boxes.
Status-based report 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 in such a way 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/pages/createpage.action?spaceKey=dlp&title=Concept%20of%20a%20field%20%28r%29&linkCreation=true&fromPageId=298288087).
> ℹ️
> ℹ️ Fields are available for all tasks (including [basic tasks](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297702042)).
**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 (e.g. BoxEditor, BoxAdmin) as they are visible only in Box type configuration but those settings might affect the User's work with the boxes.
### Customization
## Box details
Details about the Box resulting from its Box type settings can be checked by any user 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/297538577) section.
The following Box information columns are available on the Overview module:
- [Period mode](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297636248)
- [Sequentiality](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297636248)
- Created date
- [Scope type](https://appfire.atlassian.net/wiki/spaces/DLP/pages/296982489)
**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 type of Program Increment Box type → now 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](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297930799)
You can also add an **Archived **column to the view. Boxes are only visible in the following **View** settings:
Get the most information out of your data! Data visible in the columns of the Overview module provides you with high-level insight into your data. Modify the view to make sure it best meets your needs.
> Macro (anchor)
## Closed date column
**The closed date column** provides a possibility to compare the End date to the date of actual closing (changing the status to "Closed"). The user can add a 'Closed Date' column on the Overview module under "Manage column".
The column is not inline-editable and has the same aggregations as other types of the Date type i.e. None, Minimum, 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](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297634969) of Boxes is active
- you want to activate the [auto-archiving of Boxes](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297634969) - 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/298093463) using the "Inactive For" column.
> Macro (toc)
## Introduction
Get the most information out of your data! Data visible in the columns of the Overview module provides you with high-level insight into your data. Modify the view to make sure it best meets your needs.
## Box vs task data columns
**Box associated columns** show data associated with Boxes (not tasks) and are visible in the Overview module only.
**Task associated columns **show the aggregation of data based on individual tasks (inline editing won't be possible in the Overview module). Those columns are marked with "task" in the name:
> Macro (inline-media-image)
- 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):
> Macro (inline-media-image)
> ℹ️ Those columns are based on [built-in fields](https://appfire.atlassian.net/wiki/pages/createpage.action?spaceKey=dlp&title=Concept%20of%20a%20field%20%28r%29&linkCreation=true&fromPageId=298288087).
> ℹ️
> ℹ️ Task value fields are available for all tasks (including [basic tasks](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297702042)).
## Manage column views
In the Overview module, you can:
- **make temporary changes to an existing view**
- **update an existing column view**
- **create a new column view**
> ℹ️ Column views of the Hierarchy and Timeline are independent and must be changed separately.
### Existing views
At the top, you can find a list of available views.
You can freely switch between the views, as it won't affect other users.
### Temporary changes to the current view
Any user can temporarily modify the current view.
When you make changes to the active (in-use) column view:
- a red asterisk appears next to the column view name
- when you open the dropdown, you see the **current view is modified **warning
#### Restore
To undo the temporary modifications use the **Restore **option:
> Macro (inline-media-image)
### Edit existing views
To permanently update a column view hit the 'save' icon
> Macro (inline-media-image)
1. Select a view from the drop-down at the top (only an active view can be modified)
2. Add/remove columns
3. Click the **Save **icon
### **Create a new column view**
Edit a current view and use the "save as" option to save it as a new column view.
### Go to Box Configuration to manage column views
Full management of the Column views, including deleting Views, can be done in the [Box Configuration](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297572218).
### **Reorder columns**
Left-click on the column name (hold the button) and drag the column into a new position.
### **Customize columns**
Click on the wrench icon next to a column name; an additional drop-down menu will appear.
Customization options vary depending on the column.
Non-customizable columns:
- Fav
- Icon
- ID
- Name
- Type
### **Custom column **
Go to [Box Columns](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297573377) to create your own custom fields that you can use as columns in the Overview module to see the most important information and metrics related to your Project, Portfolio, or any other type of box you want to manage.
## Inline editing of box attributes
You can use inline editing to edit values directly in the Overview module.
Example:
> Macro (inline-media-image)
**Limitations**
Not all box attributes are editable.
**Closed** and **Archived** boxes - box attributes can't be edited.
## Aggregated Box status
Aggregated Box status is calculated for all Boxes.
Status-based report 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 in such a way 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 %
In the example below, the value is based on the actual cost of tasks in Boxes.
### Box associated vs task associated
**Box associated columns** are visible in the Overview module only.
For the **task associated columns**, Inline editing won't be possible in the Overview module (which shows the aggregation of data based on individual 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):
> Macro (inline-media-image)
**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:
- Gantt
- Scope
- Board
If you want to change the details of already planned tasks (tasks that are shown as cards assigned to sub-Boxes on the left) change the filtering options in the Backlog to display all tasks.
> ℹ️ Those columns are based on [built-in fields](https://appfire.atlassian.net/wiki/pages/createpage.action?spaceKey=dlp&title=Concept%20of%20a%20field%20%28r%29&linkCreation=true&fromPageId=298288087).
> ℹ️
> ℹ️ Fields are available for all tasks (including [basic tasks](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297702042)).
### 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
Additional Task calculated fields:
- Story Points
- Progress
Details about the Box resulting from its box type settings are known to an operational user (e.g. BoxEditor, BoxAdmin) as they are visible only in Box type configuration but those settings might affect the User's work with the boxes.
### Customization
## Box details
Details about the Box resulting from its Box type settings can be checked by any user 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/297538577) section.
The following Box information columns are available on the Overview module:
- [Period mode](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297636248)
- [Sequentiality](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297636248)
- Created date
- [Scope type](https://appfire.atlassian.net/wiki/spaces/DLP/pages/296982489)
**The scope type column shows the actual scope type of a Box **(which is set during Box creation and cannot be changed later).
Use case:
- A Program Increment was created. At the time the "Program Increment" Box type was set to "Sub"
- An admin changed the scope type of Program Increment Box type → now 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](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297930799)
You can also add an **Archived **column to the view:
> Macro (inline-media-image)
Boxes are only visible in the following View settings:
> Macro (inline-media-image)
Get the most information out of your data! Data visible in the columns of the Overview module provides you with high-level insight into your data. Modify the view to make sure it best meets your needs.
> Macro (anchor)
## Closed date column
**Closed date column** provides a possibility to compare the End date to the date of actual closing (changing the status to "Closed"). The user can add a 'Closed Date' column on the Overview module under "Manage column".
The column is not inline-editable and has the same aggregations as other types of the Date type i.e. None, Minimum, Maximum.
## Inactive For
Add the **"Inactive For"** column to see when the Box has been used for the last time.
This information is useful when:
- [auto-archiving](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297634969) of Boxes is active
- you want to activate the [auto-archiving of Boxes](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297634969) - 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/298093463) using the "Inactive For" column.
