...
Activate automation
Box level
From the box level, Box Admins can configure the field mapping for a project using the “Field sync configuration” option.
The “Field sync configuration” option is visible only when all tasks in a box are from one Jira project.
...
Info |
---|
For more information, see the Field mapping page. |
Method 1:
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Note |
---|
If there are tasks from a few Jira projects in one box and the projects have separate custom configurations set, tasks in one box may behave differently according to the rules configured for the project they are in). |
Method 2:
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
App configuration level
The field mapping can also be also configured from the global configuration level on the App configuration > General > Fields page.
...
The table below presents the most popular field mapping scenarios.
Field mapping | Description |
---|---|
Start Date = Start Date End Date = End Date | Dates in BigPicture are synchronized with dates in Jira (the default mode). |
Start Date = Not synchronized End Date = Not synchronized | Dates in BigPicture are not synchronized with dates in Jira. |
Start Date = Original Estimate One-way sync = Start Date End Date = End Date | Changes made to the “Original Estimate” field update the “Start Date” field. |
Start Date = Start Date End Date = Original Estimate One-way sync = End Date | Changes made to the “Original Estimate” field update the “End Date” field. |
Start Date = Start Date End Date = Time Spent + Remaining Estimate One-way sync = End Date | Changes made to the “Remaining Estimate” field can update the “End Date” field. Time logged on a task can update the “End Date” field. |
You can also synchronize the “Start Date” and “End Date” fields with different fields, e.g., “Due Date”.
...