Concept of a field
- Anna Ciepłota
- Magdalena Szpunar
Introduction
BigPicture visualizes Information based on the tool connections you have set up. Values of fields in monday, or Trello must be mapped to fields available within BigPicture. Information about the data source can be listed in the “Origin” column and shown as an appropriate icon.
There are two possible field options:
Native external tool fields - they display the value from an external platform; if the value is unavailable, it is left empty.
Built-in fields
Built-in fields can map columns from multiple Monday boards and take information from various Monday boards and external platforms (for example, Trello).
Column mapping rules are defined for each monday board separately.
When you add a column, the icon on the right indicates what data is shown - based on a value of a monday field or a built-in field.
Monday.com column types
Each column in monday.com is designated with a specific type. BigPicture supports the following column types from monday.com:
Date
Dependency
Dropdown
Long Text
Mirror (read-only)
Numbers
People
Status
Summary
Timeline
Text
Mapping options for built-in fields
Built-in fields can function in the following ways:
Configurable fields
Non-configurable fields
Native App fields (don't correspond to any external tool)
Fields that vary depending on the external platform (for example, the mapping of a field can be changed for monday but not for Trello; or a field exists in one external platform but not in another)
Configurable fields
For some fields, you can select the value you want to use.
You define synchronization rules on the App Configuration > General > Fields page.
For example, the “Start date” could be mapped to monday “Start date” field → in such case, the built-in end date of the App effectively displays the same value as monday start date.
Non-configurable fields
You can't change the mapping.
For example, the “Item name” field displays the Monday item’s name, which cannot be changed.
Native App fields
The field exists only in BigPicture and can't be found in monday, or Trello.
For example, in the "Color" field,
Fields that vary depending on the external tool
Some fields, depending on the external platform, may not have an easy corresponding value. For example, Assignee is easily found in monday but Trello doesn't have a corresponding field. A built-in Assignee column will not display any value for Trello cards.
Built-in fields matrix
The table below provides an overview of how built-in fields function in the App.
Task attribute | Mapped to external platform | Available for basic 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:
|