Meet the new BigPicture navigation
A faster, smarter, and more intuitive way to work is here. We’ve redesigned BigPicture navigation to give you a smoother experience and better access to what matters most.
→ Discover what’s new, explore key improvements, and review feature name updates on the New navigation page.
→ The rollout will happen gradually, and the previous navigation will be retired in September 2026.
Mapping options for built-in fields
Mapping options for built-in fields (old navigation)
Built-in fields can function in the following ways:
Configurable fields (e.g., End Date)
Non-configurable fields (e.g., summary)
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 Jira 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.
For example, you define synchronization rules on the App Configuration > General > Fields page. The “End date” field could be mapped to the Jira “Due date” field. In such cases, the app's built-in end date effectively displays the same value as the Jira due date.
Mapping options
Available options vary across external platforms (something can be ‘mappable’ in Jira but not in Trello). You can change the mapping of an “End date” for Jira and decide to use the “Due date” Jira value as an end date, but you can’t change the settings for Trello.
Effectively, the built-in “End date” field will display:
For Jira, what has been specified in the App Configuration (in the example below, “Due date” has been used).
Trello due date (Trello doesn’t have an “End Date” - due date will always be used to populate the built-in “End date” field).
Non-configurable fields
For non-configurable fields, you can’t change the mapping.
For example, Summary in Jira = summary built-in, and this cannot be changed. You can’t decide that a built-in “summary” will display “description” or anything else. The built-in summary will always display the same value as the Jira summary.
Native app fields
Native fields exist only in the App and can’t be found in Jira, Trello, or any other connected tool.
For example, the “Color”, and “Task ID” fields.
Some native fields, such as “Milestone,” can be mapped to external tools in configuration.
Fields that vary depending on the external tool
Some fields may not have a straightforward corresponding value on the external platform. For example, Assignee is easily found in Jira (the built-in field can display the value), but Trello doesn’t have a corresponding field (members can be added to a card, but no single person is assigned). This is why a built-in Assignee column will not display any value for Trello cards. Basic Tasks also don’t have an assignee listed in the column.
Mapping options for built-in fields (new navigation)
Built-in fields can function in the following ways:
Configurable fields (e.g., End Date)
Non-configurable fields (e.g., summary)
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 Jira 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.
For example, you define synchronization rules on the App Configuration > General > Fields page. The End Date field could be mapped to the Due Date field in Jira. In such cases, BigPicture’s built-in end date effectively displays the same value as the Jira due date.
Available options vary across external platforms (some fields can be synced in Jira but not in Trello). You can change the mapping of an End Date for Jira and decide to use the Due Date Jira value as an end date, but you can’t have the same settings for Trello.
Effectively, the built-in End Date field will display:
For Jira: The value from the field that was specified in the App Configuration.
For Trello: Trello due date (Trello doesn’t have an End Date; a Due Date will be used to sync the built-in End date field.
Non-configurable fields
For non-configurable fields, you can’t change the mapping.
For example, the Summary field in Jira syncs with the Summary built-in field in BigPicture, and this cannot be changed. You cannot change the mapping of a built-in Summary field to Description or any other field. The built-in Summary in BigPicture will always display the same value as the Summary in Jira.
Native app fields
Native fields exist only in BigPicture and cannot be found in Jira, Trello, or any other connected tool.
For example, the Color and Task ID fields. When you search for them in the Add or edit columns dropdown, you will see that there is no equivalent field in the connected tool.
Some native fields, such as Milestone, can be mapped to external tools in configuration.
Fields that vary depending on the external tool
Some fields may not have a straightforward corresponding value on the external platform.
For example, Assignee can be found in Jira (the built-in field can display the value), but Trello does not have a corresponding field (members can be added to a card, but no single person is assigned). This is why a built-in Assignee column will not display any value for Trello cards.
BigPicture tasks also do not have an assignee listed in the task structure column.