Roadmap - Synchronization settings
Synchronization lets you keep in sync the due dates in OKR Roadmap with corresponding Jira issue fields. Settings defined here apply to all issues which were added to OKRs.
When enabled, task synchronization is bi-directional and instant. For example, if you move an issue using the OKR Roadmap, your issue’s "Start Date" and "End Date" fields will be updated. Conversely, if you edit the "Start Date" or "End Date" fields via the Jira issue view, the issue changes will be updated and visible in the OKR Roadmap.
Only Plugin administrators can access this page.
Migrating existing values
When you apply a new mapping schema, please select the synchronization type and corresponding values will be moved to the new fields.
You can set Oboard data as a primary source so that all the values from Oboard fields will be migrated (synced) to the new Jira field.
Or you can set Jira as a primary source so that all the values from the currently mapped Jira field will be migrated (synced) to the new Jira field and Oboard field.
Additionally, you can save existing values from overriding by null fields during migration when the toggle is ON:
Custom synchronization settings per the Jira project
Customize your synchronization settings by creating a separate configuration scheme for a Jira project. When you do that, general settings will no longer apply to this project.
Exclude project from synchronization
You can exclude a project from synchronization by creating a custom mapping for a specific project with “Not synchronized” values.
Read more about user setting for Roadmap here: What is an OKR roadmap?