Field mapping
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. Read more about the field mapping on the Fields page.
Synchronization of BigPicture values with a task source:
Short explanation → Values stored in a connected integration (such as Jira) can be synchronized with BigPicture.
Example → Jira field 'Original Estimate' synchronized with BigPicture 'end date.'
Values that aren't being synchronized are stored exclusively in the BigPicture database.
Conditions
The scope definition of a box must be simple - 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.
Who can edit field mapping?
To change the field mapping, you must have sufficient permissions in BigPicture and Jira.
Acceptable BigPicture permissions:
Box Admin
App Admin
App resource admin
Acceptable Jira permissions:
Jira project admin
Jira admin
For more than one project in a box, you need Jira admin permission to preview or edit field mapping.
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 on the wrench icon at the top right.
Select Field mapping from the list.
Field mapping
Current setup info
In the pop-up, 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.
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)
The default configuration can be accessed and modified by an App Admin 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 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.