| Info |
|---|
For boxes based on a single Jira project, field mapping can be easily changed:
 |
...
Synchronization of BigPicture values with a task source
...
Example → Jira field 'Original Estimate' synchronized with BigPicture 'end date.'.
Values that aren't being synchronized are stored exclusively in the BigPicture database.
...
The scope definition of a box must be simple - limited to a single Jira project. 
...
Who can edit field mapping?
To change the field mapping, you need to must have sufficient permissions in both BigPicture and Jira.
Acceptable BigPicture permissions:
Box Admin
App Admin
App resource admin
Acceptable Jira permissions:
Jira project admin
Jira admin
How to access the field sync configuration?
From a box context
Click on the wrench icon at the top right.
Select Field sync configuration from the list.
...
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 sync configuration from the list.
...
Field sync configuration
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 is using 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 is using uses the custom configuration settings, it means a separate, independent mapping exists for a project. 
...
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 go back return to using the default configuration.
...
The default configuration can be accessed and modified by an App Admin in the App Configuration > General > Fields section.
...