Histórico da Página

h1. Introduction

TODO, What is the audience of this document?

h1. Synchronization

h2. Synchronization Direction

TODO, speak about synchronization direction options and consequences.

h2. Synchronization Options

TODO, speak about synchronization options available for each element.

h2. Sychronization Example

This section present a typical synchronization environment treated by Mizura.

Assume that a [_LEFT_TO_RIGHT_|http://3layer.com.br/fisheye/browse/treelayer-mizura/trunk/mizura/src/br/org/treelayer/mizura/mapper/enums/SyncDirection.java?r=HEAD] synchronization operation is used, where _left_ elements are Enterprise Architect usecases and _right_ elements are Jira issues.

The elements involved in this example are displayed below:

{viewxls:name=3layer - public - mizura - usecases - support materials.xlsxlsx}

|| Left element (EA usecases) || Last update || Right element (JIRA issues) || Last update || Comment ||
| usecase UC001 | 10:00:00 | issue MZ-1 | 09:00:00 | Usecase and issue are connected, and usecase information is more recent |
| usecase UC002 | 10:00:00 | issue MZ-2 | 11:00:00 | Usecase and issue are connected, and issue information is more recent |
| usecase UC003 | 10:00:00 | {center}-{center}  | {center}-{center}  | A usecase exist, but not an equivalent issue |
| {center}-{center}  | {center}-{center}  | issue MZ-4 | 11:00:00 | A jira issue exist, but not an equivalent usecase |
| {center}(x){center} | {center}(x){center} | issue MZ-5 | 11:00:00 | A preexistent usecase was deleted since the last synchronization, and a issue stay holding the given usecase identificator information |

Once synchronization occurs, the following operations are performed in the environment, regard each [SyncOption|http://3layer.com.br/fisheye/browse/treelayer-mizura/trunk/mizura/src/br/org/treelayer/mizura/mapper/enums/SyncOption.java?r=HEAD] configuration attached to the destination element:

|| Usecase || UC001 at 10:00:00 || UC02 at 10:00:00 || UC003 at 10:00:00 || {center}-{center} || {center}(x){center} ||
|| Issue || MZ-1 at 09:00:00 || MZ-2 at 11:00:00 || {center}-{center} || MZ-4 at 11:00:00 || MZ-5 at 11:00:00 ||
| ADD | None | None | Issue created | None | None |
| ADD_UPDATE \\ | Issue updated \\ | Issue updated \\ | Issue created \\ | None \\ | None \\ |
| ADD_UPDATEIFNEW \\ | Issue updated \\ | None | Issue created \\ | None \\ | None \\ |
| ADD_UPDATE_DELETE \\ | Issue updated \\ | Issue updated \\ | Issue created \\ | None \\ | Issue deleted \\ |
| ADD_UPDATE_DELETEWITHPURGE \\ | Issue updated \\ | Issue updated \\ | Issue created \\ | Issue deleted \\ | Issue deleted \\ |
| ADD_UPDATEIFNEW_DELETE \\ | Issue updated \\ | None \\ | Issue created \\ | None\\ | Issue deleted \\ |
| ADD_UPDATEIFNEW_DELETEWITHPURGE \\ | Issue updated\\ | None \\ | Issue created \\ | Issue deleted \\ | Issue deleted \\ |
| ADD_DELETE \\ | None \\ | None \\ | Issue created \\ | None \\ | Issue deleted \\ |
| ADD_DELETEWITHPURGE \\ | None | None \\ | Issue created\\ | Issue deleted \\ | Issue deleted \\ |
| UPDATE \\ | Issue updated \\ | Issue updated \\ | None \\ | None \\ | None \\ |
| UPDATE_DELETE \\ | Issue updated \\ | Issue updated \\ | None \\ | None | Issue deleted \\ |
| UPDATE_DELETEWITHPURGE \\ | Issue updated \\ | Issue updated \\ | None\\ | Issue deleted \\ | Issue deleted \\ |
| UPDATEIFNEW \\ | Issue updated \\ | None \\ | None \\ | None \\ | None \\ |
| UPDATEIFNEW_DELETE \\ | Issue updated \\ | None \\ | None \\ | None | Issue deleted \\ |
| UPDATEIFNEW_DELETEWITHPURGE \\ | Issue updated \\ | None \\ | None \\ | Issue deleted \\ | Issue deleted \\ |
| DELETE \\ | None \\ | None \\ | None \\ | None \\ | Issue deleted \\ |
| DELETEWITHPURGE \\ | None \\ | None \\ | None \\ | Issue deleted \\ | Issue deleted \\ |