---
title: "One-way sync of start/end date"
canonical: "https://support.appfire.com/space/BGc/3539665978/One-way%20sync%20of%20start%2Fend%20date"
format: markdown
---
> Macro (aura-html)

> ℹ️ Refer to the [https://appfire.atlassian.net/wiki/spaces/BGdcDRAFT/pages/2613557147](https://appfire.atlassian.net/wiki/spaces/BGdcDRAFT/pages/2613557147) page for more information.

The start and end date fields can be mapped and unidirectionally synchronized with an additional Jira field. This will result in a one-way data sync from BigGantt to Jira.

## Access the one-way sync fields

To see a one-way sync field, change the start/end date field mapping to a time tracking field and save the changes. A corresponding one-way sync field will appear.

The **one-way sync start date field** is visible only when:

- start date field is synchronized with the **Original Estimate **field.

The **one-way sync end date field** is visible only when:

- The end date field is synchronized with the **Original Estimate** field.
- or, the end date field is synchronized with the  **Time Spent + Remaining Estimate **fields.

![Field mapping settings in BigPicture for one-way sync.](media://8797b97a-969c-488f-8540-4c8e5d42d692)

## Configure the Start/End date one-way sync

The one-way sync from BigGantt to Jira does not disrupt the functioning of the Start/End date fields. 

First, configure the standard field mapping for the Start/End date. For example, you can map the BigGantt Start date to the Jira Start date and the BigGantt End date to Jira Time Spent + Remaining Estimate.

Then, map the BigGantt one-way sync end date field with another Jira field, such as the Jira Due date.

> ℹ️ - The one-way sync mapping follows the same rules as the standard (bi-directional) field mapping, meaning you **cannot select the same field** for both the End Date and the one-way sync End Date.
> ℹ️ - Only simple date and time fields can be selected for the one-way sync mapping. Fields such as Time Spent and Remaining Estimate are not available.

![Once way sync example.](media://ef8e77ab-bddf-46df-a59b-fd3ebdd0f58d)

This will result in the following:

- The tasks' end dates in BigGantt are based on Jira’s Time Spent + Remaining Estimate.
- BigGantt updates the tasks' end dates and visualizes them on the timeline based on those settings.
- BigGantt updates the Due date field value in Jira based on the End date field value.

Such synchronization is uni-directional, so changing the Due date in Jira does not change the end date in BigGantt.