---
title: "Field mapping."
canonical: "https://support.appfire.com/space/DLP/297635027/Field%20mapping."
format: markdown
---
| **Contents:**<br>> Macro (toc) |
| --- |

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](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297767423).

**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](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297767423) page.

![image2022-3-23_8-40-39.png](media://9b99cc2f-905c-4c46-b0a6-f3c6a9ddc01a)

## 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.

![image-20240209-093351.png](media://c9e32c15-568d-414a-bff9-c8fedd4b7084)

## How to access the field mapping?

### From a box context

**Method 1:**

> Macro (excerpt)
> 
> 1. Click the **wrench icon** at the top right.
> 2. Select **Field mapping** from the list.

**Method 2:**

> Macro (excerpt)
> 
> 1. Click the **cog** icon.
> 2. Click the **Field mapping** button.
> 3. Now, you can:
>   1. Restore default settings
>   2. Reset to defaults
>   3. Make changes
> 4. When ready, click **Save**.

### From a Jira project context

Go to a **Jira project:**

1. On the left, select the **BigPicture widget**.
2. Click on the **wrench icon** at the top right.
3. Select **Field mapping** from the list.

![image-20240207-090141.png](media://04ac2741-a291-4a02-a6ed-8ca31d14715f)

## Field mapping

### Current setup info

In the pop-up, you can see the current field mapping of a project:

![image](media://298630e5-6616-46ae-8298-238a65af0564)

At the top, you can see info regarding the current setup. The message lets you know if a **[custom configuration](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297767423/Fields.#Custom-mapping-(per-Jira-project))** (custom mapping) exists for a project.

If a project uses the **default configuration** settings, it means a [custom configuration](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297767423/Fields.#Custom-mapping-(per-Jira-project)) doesn't exist for a project yet. The project is using the default mapping. 

![image](media://d873fd39-e743-4ec6-85c7-9c64d6423025)

If a project uses the **custom configuration** settings, it means a separate, independent mapping exists. 

![image](media://41b4ccb7-f134-4b08-bdbc-ca0d81dc8c5e)

### Make changes

When you modify the mapping and save changes:

- The custom configuration is created, **OR**
- The existing custom configuration is updated.

![image-20240207-090410.png](media://6f7b5596-3deb-482e-86c6-c5ba9964e856)

### Restore default settings

You can always remove the custom configuration and return to the default configuration.

![image-20240207-090505.png](media://799f9870-d4bc-4d75-b970-cd425bb5102c)

### Reset to defaults

If you click **Reset to defaults**, all custom settings will be overwritten with default settings. 

> ⚠️ The action **CANNOT** be undone.

![image-20240207-090608.png](media://a5b3f8e2-55d8-46c0-b142-50459ddd18c9)

### Field mapping (App configuration)

The default configuration can be accessed and modified by an App Admin in the [App Configuration > General > Fields](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297767423) section.

![image](media://849b770b-1e77-4250-8132-14ff3027884c)

### 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.