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.
Fields
Fields (old navigation)
This section changes the task field synchronization settings and enables additional features, such as comments and notifications, which facilitate team communication.
Modify the mapping of this section to synchronize task attributes with appropriate external tool fields. When enabled, task synchronization is bi-directional and instant. For example, if you move a task using the Gantt module, the Start Date and End Date fields will be updated. Conversely, if you edit the Start Date or End Date fields via the Jira card of a task, the task changes will be updated and visible in the Gantt module.
General mapping affects all tasks unless you add custom mapping for specific projects.
For boxes based on a single Jira project, field mapping can be easily changed:
From the level of an individual box
Directly from a box context and a Jira project context
For boxes based on multiple Jira projects, the field mapping is configured on the App configuration > General > Fields page.
Synchronization of the app values with a task source:
Values stored in a connected integration (such as Jira) can be synchronized with the app. For example, the Original Estimate Jira field can be synchronized with the app’s End Date field.
Values that aren't being synchronized are stored exclusively in the app’s database.
Conditions
The scope definition of a box must be simple, meaning limited to a single Jira project.
If a box is based on multiple Jira projects and you click the Field mapping button, you are redirected to the App configuration > General > Fields page.
Security and access
To change the field mapping, you must have sufficient permissions in the app and Jira.
Acceptable app permissions:
Box Admin
App Admin
App Resource Admin
Acceptable Jira permissions:
Jira project Admin
Jira Admin
If there is more than one project in a box, you need Jira admin permission to preview or edit field mapping.
Click the wrench icon at the top right and select General from the drop-down list.
Next, go to the Fields tab.
General mapping
You can’t use the same field more than once. For example, If the Due Date field is mapped as the End Date of your task, you cannot select this field for any other mapping within a configuration of the same Jira Project. This applies to the following filed mappings:
Start Date
End Date
Baseline Start Date
Baseline End Date
Every connection has separate settings used for mapping. That includes each Jira instance, Trello workspace, etc.
Each instance connection can be expanded. Upon expanding, you can see the field mapping settings of the particular instance.
Platform differences
Field mapping possibilities depend on the product (Jira vs. Trello).
Jira:
Trello:
Custom mapping (per Jira project)
Customize your synchronization settings by creating a separate configuration scheme for a Jira project. When you do that, general settings will no longer apply to this project.
Custom synchronization is created per Jira project - not per box. This means you can have tasks from different projects with different mappings in the same box.
To add custom mapping for a selected project:
Switch to the Custom mapping tab.
Click Add Project.
Select a project from the drop-down menu.
Click Add and configure.
Customize synchronization settings for a project.
Click Save to confirm.
The list of projects with custom synchronization is displayed once the new synchronization is saved.
When you map a new Trello instance connection, its Start Date and End Date fields are set to Not Synchronized by default.
This means that when you change the dates of your Trello tasks in BigPicture, the changes will not be transferred to Trello (and vice versa).
The mappings need to be set manually when connecting with Trello.
You can leave the Not Synchronized status if you don't want to set dates from the BigPicture level.
How to access the field mapping?
From a box context
Method 1:
Click the wrench icon at the top right.
Select Field mapping from the list.
Method 2:
Click the cog icon.
Click the Field mapping button.
Now, you can:
Restore default settings
Reset to defaults
Make changes
When ready, click Save.
From a Jira project context
Go to a Jira project:
On the left, select the BigPicture widget.
Click the wrench icon at the top right.
Select Field mapping from the list.
Field mapping
Current setup info
In the dialog, you can see the current field mapping of a project:
At the top, you can see info regarding the current setup. The message lets you know if a custom configuration (custom mapping) exists for a project.
If a project uses the default configuration settings, it means a custom configuration doesn't exist for a project yet. The project is using the default mapping.
If a project uses the custom configuration settings, it means a separate, independent mapping exists.
Make changes
When you modify the mapping and save changes:
The custom configuration is created, OR
The existing custom configuration is updated.
Available fields
In some cases correct fields are still missing on Jira instances created after Jan 1, 2026, due to changes to Atlassian API behaviour. We are currently working on a fix that will be provided shortly.
A Jira field has to have a specific type to be available to be chosen for synchronization:
BigPicture Field | Compatible Jira Field Type(s) | Technical Specification & Sync Logic |
Start date |
| Date types: Standard sync. Original Estimate: BP calculates start based on task position/duration. |
End date |
| Date types: Standard sync. Remaining Estimate: BP uses this to calculate the task bar’s end point. |
Baseline start/end |
| Strict requirement: Must be a date type to store a static schedule "snapshot." |
Team Code |
| Labels (Recommended): Syncs as Select List: Jira option names must match BP Team IDs exactly. |
Milestone field |
| Checkbox: Requires a single-option checkbox (e.g., "Yes"). |
Story Points |
| Number: Standard Story Point sync. Time Tracking: BP converts time to "points" based on Task Resource settings. |
Required Skills |
| Labels: Syncs as Note: Spaces are replaced by underscores (e.g., |
Actual / Est. Cost |
| Used for financials modules; requires numeric custom fields. |
Progress |
| Number: Uses 0–100 values. Time Tracking: Syncs based on "Time Spent" vs. "Original Estimate." |
Scheduling mode |
| Jira options must be exactly: |
The API Filter: BigPicture identifies available fields by combining results from
/field(classic) and/field/search(modern/team-managed). If a field doesn't appear, ensure it matches the types in the table above.The Sync Prefixes: When using Labels for Teams or Skills, BigPicture uses the
#delimiter (team#andskill#). This allows it to coexist with other Jira labels without overwriting them.Time Tracking Fields: You may see Jira's
Time TrackingorOriginal Estimatefields available in several dropdowns (like Start Date or Story Points). This is because BigPicture can automatically convert "Time" into "Dates" or "Points" based on your project's working calendar. While supported, we recommend using standard Date Picker and Number fields for the most predictable results.
Restore default settings
You can always remove the custom configuration and return to the default configuration.
Reset to defaults
If you click Reset to defaults, all custom settings will be overwritten with default settings.
The action CANNOT be undone.
Field mapping (App configuration)
An App Admin can access and modify the default configuration in the App Configuration > General > Fields section.
Field mapping reminders
The app prompts you to check the field mapping:
when you add or remove projects in the scope
when you make an edit to a built-in field that does not have mapping.
Limitations
Box editors and box viewers have read-only access to the field mapping of a box. The field mapping option is greyed out for them.
Fields (new navigation)
This section changes the task field synchronization settings and enables additional features, such as comments and notifications, which facilitate team communication.
Modify the mapping of this section to synchronize task attributes with appropriate external tool fields. When enabled, task synchronization is bi-directional and instant. For example, if you move a task using the Gantt module, the Start Date and End Date fields will be updated. Conversely, if you edit the Start Date or End Date fields via the Jira card of a task, the task changes will be updated and visible in the Gantt module.
General mapping affects all tasks unless you add custom mapping for specific projects.
For boxes based on a single Jira project, field mapping can be easily changed:
From the level of an individual box
Directly from a box context and a Jira project context
For boxes based on multiple Jira projects, the field mapping is configured on the App configuration > General > Fields page.
Synchronization of the app values with a task source:
Values stored in a connected integration (such as Jira) can be synchronized with the app. For example, the Original Estimate Jira field can be synchronized with the app’s End Date field.
Values that aren't being synchronized are stored exclusively in the app’s database.
Conditions
The Add work items from Jira settings of a box must be simple, meaning limited to a single Jira space.
If a box is based on multiple Jira projects and you click the Field mapping button, you are redirected to the App configuration > General > Fields page.
Security and access
To change the field mapping, you must have sufficient permissions in the app and Jira.
Acceptable app permissions:
Box Admin
App Admin
App Resource Admin
Acceptable Jira permissions:
Jira project Admin
Jira Admin
If there is more than one project in a box, you need Jira admin permission to preview or edit field mapping.
Click the wrench icon at the top right and select General from the drop-down list.
Next, go to the Fields tab.
General mapping
You can’t use the same field more than once. For example, If the Due Date field is mapped as the End Date of your task, you cannot select this field for any other mapping within a configuration of the same Jira Project. This applies to the following filed mappings:
Start Date
End Date
Baseline Start Date
Baseline End Date
Every connection has separate settings used for mapping. That includes each Jira instance, Trello workspace, etc.
Each instance connection can be expanded. Upon expanding, you can see the field mapping settings of the particular instance.
Platform differences
Field mapping possibilities depend on the product (Jira vs. Trello).
Jira:
Trello:
Custom mapping (per Jira project)
Customize your synchronization settings by creating a separate configuration scheme for a Jira project. When you do that, general settings will no longer apply to this project.
Custom synchronization is created per Jira project - not per box. This means you can have tasks from different projects with different mappings in the same box.
To add custom mapping for a selected project:
Switch to the Custom mapping tab.
Click Add Project.
Select a project from the drop-down menu.
Click Add and configure.
Customize synchronization settings for a project.
Click Save to confirm.
The list of projects with custom synchronization is displayed once the new synchronization is saved.
When you map a new Trello instance connection, its Start Date and End Date fields are set to Not Synchronized by default.
This means that when you change the dates of your Trello tasks in BigPicture, the changes will not be transferred to Trello (and vice versa).
The mappings need to be set manually when connecting with Trello.
You can leave the Not Synchronized status if you don't want to set dates from the BigPicture level.
How to access the field mapping?
From a box context
Method 1:
Click the wrench icon at the top right.
Select Field mapping from the list.
Method 2:
Click the cog icon.
Click the Field mapping button.
Now, you can:
Restore default settings
Reset to defaults
Make changes
When ready, click Save.
From a Jira project context
Go to a Jira project:
On the left, select the BigPicture widget.
Click the wrench icon at the top right.
Select Field mapping from the list.
Field mapping
Current setup info
In the dialog, you can see the current field mapping of a project:
At the top, you can see info regarding the current setup. The message lets you know if a custom configuration (custom mapping) exists for a project.
If a project uses the default configuration settings, it means a custom configuration doesn't exist for a project yet. The project is using the default mapping.
If a project uses the custom configuration settings, it means a separate, independent mapping exists.
Make changes
When you modify the mapping and save changes:
The custom configuration is created, OR
The existing custom configuration is updated.
Available fields
In some cases correct fields are still missing on Jira instances created after Jan 1, 2026, due to changes to Atlassian API behaviour. We are currently working on a fix that will be provided shortly.
A Jira field has to have a specific type to be available to be chosen for synchronization:
BigPicture Field | Compatible Jira Field Type(s) | Technical Specification & Sync Logic |
Start date |
| Date types: Standard sync. Original Estimate: BP calculates start based on task position/duration. |
End date |
| Date types: Standard sync. Remaining Estimate: BP uses this to calculate the task bar’s end point. |
Baseline start/end |
| Strict requirement: Must be a date type to store a static schedule "snapshot." |
Team Code |
| Labels (Recommended): Syncs as Select List: Jira option names must match BP Team IDs exactly. |