Contents:
|
---|
About the one-way sync of Start/End date fields
Info |
---|
Refer to this the page for more information about task dates based on estimates for more information. |
The
...
The end date field is synchronized with: Original Estimate
The end date field is synchronized with: Time Spent + Remaining Estimate
The one-way sync start date field is visible only when:
...
start and end date fields can be mapped and uni-directionally synchronized with an additional Jira field. This will result in a one-way data sync from BigPicture 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
...
The Start/End date can be mapped and uni-directionally synchronized with an additional Jira field.
This is a one-way sync from the App to Jira.
...
This is a one-way sync. From BigPicture/BigGantt 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:
end date field is synchronized with the Original Estimate field.
or, the end date field is synchronized with the Time Spent + Remaining Estimate fields.
...
Configure the Start/End date one-way sync
The one-way sync from BigPicture to Jira does not disrupt the functioning of the Start/End date fields.
First, you set up configure the standard field mapping for the Start/End date - based on that, the field value of the Start/End date field is established. Then, the App takes the Start/End date value and updates a selected Jira field.
For example:
...
. For example, you can map the BigPicture Start date to the Jira Start date and the BigPicture End date to Jira Time Spent + Remaining Estimate.
...
The App uses the End date value to visualize tasks on the timeline.
...
The End date field value is used to update the value of the Due date Jira field.
Synchronization is uni-directional, so changing the Due date in Jira won't alter the end date in the App.
The additional Then, map the BigPicture one-way sync end date field with another Jira field, such as the Jira Due date.
Info |
---|
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
This will result in the following:
The tasks' end dates in BigPicture are based on Jira’s Time Spent + Remaining Estimate.
BigPicture updates the tasks' end dates and visualizes them on the timeline based on those settings.
BigPicture 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 BigPicture.