Bulk, Force Calculated CF, ReSync

Bulk synchronization

Bulk Synchronization action allows to synchronize many issues from filter. 

  • When you have existing issues to be replicated.
  • To push old/historical issues.
  • Archive issues from time to time on different JIRA instance.


 Only Issues with Create Remote (see Synchronization Events, JQL, Triggers) button can be synchronized by Bulk Synchronization.




Force field update

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). 
It can happen that calculation and value assignment is done after IssueSYNC stores update request. 


In this case you can extend IssueSYNC's default behaviour. 
The synchronization flow will look like this: 

  1. Standard update event.
  2. New delayed queue entry is being formed.
  3. On synchronizing time (see Cron timer configuration) new update request is being created with field values present at time of synchronization time.
  4. Two instead of one update request are sent to remote JIRA instance. 
  5. Second (delayed) update will override field values assigned in first (default) request.

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).



Re-Synchronization

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?

  • updates all fields to state, which remote issue fields are at
  • check for any differences in comments (if any has been found, IssueSYNC pulls remote ones)
  • check for any differences in attachments (if any has been found, IssueSYNC pulls remote ones)
  • check for any status difference (if any has been found, IssueSYNC will try to reach remote issue status by performing required transitions)


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.