Bulk Synchronization action allows to synchronize many issues from filter.
Only Issues with Create Remote (see Synchronization Events, JQL, Triggers) button can be synchronized by Bulk Synchronization.
This mechanism allows you to always synchronize given fields even specific field wasn't subject of change (calculated fields).
It is provided due to support 3rd party scripts, which calculate some fields values (Script Runner / Groovy). |
In this case you can extend IssueSYNC's default behaviour.
The synchronization flow will look like this:
To turn on this feature you need to set DELAYED value to true in CONTRACT_FM table (rows corresponding to field mapping in contract configuration).
The aim of re-synchronization process is to make issues state equal in both local and remote JIRA instances.
You may want to use this feature in case of failover.
This feature will pull data from your remote JIRA instance, it support fields, comments, attachments and workflow resynchronization.
It will not create new issues or create ones, which are not present in remote JIRA instance.
What it does?
You can re-synchronize as many Synchronization Scheme as you want for given connection.
Hard re-synchronization flag - choose this to make IssueSYNC pull comments and attachments even if they're present in your local JIRA instance (it may duplicate your comments and attachments), date restriction is prioritized.
Control your re-synchronization flow - by checking this option you will list all your re-synchronizing issues, please leave it disabled if you are going to re-synchronize a lot of issues not to strain your browser.