Column View
- Anna Ciepłota
- Piotr Koszela
- Marta Golab (Deactivated)
- Magdalena Żaczek
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 meet your needs best.
Box vs task data columns
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:
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.
Task value fields are available for all tasks (including basic tasks).
Inline editing of box attributes
You can use inline editing to edit values directly in the Overview module.
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).
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 %
Box vs task data columns
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.
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.
Those columns are based on built-in fields.
Fields are available for all tasks (including basic tasks).
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 section.
The following Box information columns are available on the Overview module:
Created date
The scope type column shows the actual scope type of a Box (which is set during Box creation and cannot be changed later).
Archived boxes
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.
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 of Boxes 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 using the "Inactive For" column.