Introduction

TODO, What is the audience of this document?

Synchronization

Synchronization Direction

TODO, speak about synchronization direction options and consequences.

Synchronization Options

TODO, speak about synchronization options available for each element.

Sychronization Example

This section show typical synchronization environment treated by Mizura.

To simplify, a LEFT_TO_RIGHT synchronization operation is used, where left elements are Enterprise Architect usecases and right elements are Jira issues.

The elements involved in this example are showed below:

Left element (EA usecases)	Last update	Right element (JIRA issues)	Last update	Comment
usecase UC001	2010.02.01 10:00:00	issue MZ-1	2010.02.01 09:00:00	Usecase and issue are connected, and usecase information is more recent
usecase UC002	2010.02.01 12:00:00	issue MZ-2	2010.02.01 11:00:00	Usecase and issue are connected, and usecase information is more recent
usecase UC003	2010.02.01 14:00:00	issue MZ-3	2010.02.01 15:00:00	Usecase and issue are connected, and jira issue information is more recent
usecase UC004	2010.02.01 16:00:00			A usecase exist, but not an equivalent issue
		issue MZ-5	2010.02.01 17:00:00	A jira issue exist, but not an equivalent usecase
		issue MZ-6	2010.02.01 19:00:00	Aa existent usecase was deleted in EA since the last synchronization, and a jira issue exist with the given usecase identificator information

Once synchronization occurs, the following operations are performed in the environment:

Left element (EA usecases)	Right element (JIRA issues)	ADD	ADD_UPDATE	ADD_UPDATE_DELETE	ADD_UPDATE_DELETEWITHPURGE
usecase UC001	issue MZ-1		issue updated	issue updated	issue updated
usecase UC002	issue MZ-2		issue updated	issued updated	issue updated
usecase UC003	issue MZ-3		issue updated	issued updated	issue updated
usecase UC004		issue MZ-n created	issue MZ-n created	issue MZ-n created	issue MZ-n created
	issue MZ-5	None	None	None	issue MZ-5 deleted
	issue MZ-6	None	None	issue MZ-6 deleted	issue MZ-6 deleted