Message-ID: <1013093582.16206.1711728156402.JavaMail.appbox@confluence> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_16205_733605221.1711728156402" ------=_Part_16205_733605221.1711728156402 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
A resync, or full resynchronization, is a one-time process activ= ated manually by the user to bring Structure and some other aspect of issue= s to the same page. Resync typically scans all issues that may be affected = - contrary to the incremental synchronization, which inspects only issues t= hat have been changed.
=20For example, running resync on a Saved Filter synchronizer (in Add= em> mode) runs the related Saved Filter and makes sure all issues from= the result set are in the structure. When the same synchronizer is working= in the background, it checks only those issues that have been changed.
= =20Resync is also different from incremental synchronization in that it has= a direction. The incremental sync tries to apply changes on both&= nbsp;sides to the other side, if possible, depending on where the change ha= s happened: with JIRA Agile (GreenHopper) synchronizer, if you change the r= ank (issue position in backlog on the Planning Board), its position in the = structure is also changed; and if you change the position in the structure,= GreenHopper's rank is changed. However, when applying Resync, you need to = choose which side of the data is to be taken as the final version and which= is to be updated.
=20Resync can be run:
=20A synchronizer may support resyncing in only one direction. For example= , Saved Filter synchronizer, which adds issues from a saved filter result, = can only sync into Structure.
To run a resync:
=20Resyncing in a wrong direction may lead to data loss! Please make sure y= ou understand that you're doing the correct thing and confirm running the r= esync when a confirmation dialog appears.
If the synchronizer is currently running an incremental synchronization,= the resync will wait until it finishes.