...
The table below provides an overview of how built-in fields function in the App.
Task Attributeattribute | Mapped to External Platform external platform | Available for Basic Tasksbasic tasks | Comment |
---|---|---|---|
Icon | YES, non-configurable | YES | |
Item ID | YES, non-configurable | YES | The built-in "Item ID" column will aggregate items/tasks/card IDs from different platforms and display them in a single column. The "Item ID" field cannot be modified to display any other value. |
Item name | YES, non-configurable | YES | The “Item name” field is mapped to monday item name by default and cannot be removed. |
Start date | YES, configurable | YES | It can be mapped to the “Timeline” or “Date” column. When the “Date” column is chosen, the “End date” field has to be mapped to another “Date” column. Trello cards don't have start dates. A built-in field uses the due date value (effectively, the built-in field start and end dates of Trello cards are mapped to the due date). Basic task dates are displayed in the built-in “Start date” column. |
End date | YES, configurable | YES | It can be mapped to the “Timeline” or “Date” column. When the “Date” column is chosen, the “Start date” field has to be mapped to another “Date” column. A built-in field uses the due date value (effectively, the built-in field start and end dates of Trello cards are mapped to the due date). Basic task dates are displayed in the built-in “Start date” column. |
Baseline start date | NO | YES | |
Baseline end date | NO | YES | |
Milestone | YES, non-configurable | YES | Mapped to the “Timeline” column used for start and end dates. |
Period mode | NO | YES | |
Color | NO | YES | Native App field. It can't be mapped to display values from external tools. |
Assignee | YES, configurable | NO | It can be mapped to the “People” column. |
Status | YES, configurable | NO | It can be mapped to the “Status” column. BigPicture supports custom colors of statuses set in monday. |
Duration Calendar Days | NO | YES | Based on the number of calendar days (start to end date).
|
Duration working days | NO | YES | Based on the number of working days (non-working days excluded).
|
Outline level | NO | YES | Dynamically built Data Type - the values aren't permanently associated with tasks; the field value adjusts to reflect WBS changes. Display Options:
Outline level → shows how deep the task is in the tree structure (WBS). Sequential Index → shows where the task is located in the WBS structure (similar to the notation of the table of contents in the book) Note: filtering does not affect the Sequential Index. |
Overdue Start/End Date | NO | NO | The Overdue Start Date field calculates the difference between the current task Start Date (when the status category is To Do).
The Overdue End Date calculates the difference between the current task end date and the status category End Date (when the status category is not done).
|
Sub-box | YES | YES | The field displays the name of the sub-boxes in which the task is located (only the name of the box one level down is displayed). The field can hold more than one box name, as a task can be in multiple boxes. The field is in the ready-only mode. The field is especially useful in higher-level boxes to group tasks: |