Histórico da Página

...

Sychronization Example

This section show present a typical synchronization environment treated by Mizura.

To simplify, Assume that 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 displayed 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 10:00:00	issue MZ-2	2010.02.01 11:00:00	Usecase and issue are connected, and issue information is more recent
usecase UC003	2010.02.01 14 10:00:00	Center -	Center -	A usecase exist, but not an equivalent issue
Center -	Center -	issue MZ-3 2010.02.01 154	11:00:00	usecase UC004	2010.02.01 16:00:00 A jira issue exist, but not an equivalent usecase
Center	Center	issue MZ-5	2010.02.01 17 11:00:00

Since many synchronization options (SyncOption) can be used, each configuration is covered below:

ADD Option

Using ADD configuration option in the right side (Jira issue), after the synchronization, the system hold these values:

Once synchronization occurs, the following operations are performed in the environment, regard each SyncOption configuration attached to the destination element:

2010.02.01 09 2010.02.01 12 issue MZ2 2010.02.01 14 issue 3 2010.02.01 15 2010.02.01 16 Jira issue created issue 2010.02.01 17

Usecase	UC001 at 10:00:00	issue MZ-1	UC02 at 10:00:00	Jira issue untouched	usecase UC002	UC003 at 10:00:00	Center	-	2010.02.01 11:00:00	Jira issue untouched	usecase UC003		Center
Issue	MZ-1 at 09:00:00	MZ-	2 at 11:00:00	Jira issue untouched	usecase UC004	Center -	MZ-4 at 11:00:00	issue MZ-n	current_time		MZ-5	at 11:00:00	Jira issue untouched

Note 1: Since other issues may have been created in the interval, the term "n", in MZ-n refer a new sequence number in Jira repository. Dont worry about it, since Mizura uses a internal identifier (TODO, link to it) to synchronize elements.

Note 2: The signal "+" in timestamp column denotes that a right timestamp is, at least, greather than the left element timestamp, since synchronization always occurs over preexisting elements.

ADD_UPDATE Option

Using ADD_UPDATE configuration option in the right side (Jira issue), after the synchronization, the system hold these values:

...

Left element (EA usecases)

...

Last update

...

Right element (JIRA issues)

...

Last update

...

Comment

...

usecase UC001

...

2010.02.01 10:00:00

...

issue MZ-1

...

current_time

...

Jira issue fields updated

...

usecase UC002

...

2010.02.01 12:00:00

...

issue MZ-2

...

current_time

...

Jira issue fields updated

...

usecase UC003

...

2010.02.01 14:00:00

...

issue MZ-3

...

current_time

...

Jira issue fields updated

...

usecase UC004

...

2010.02.01 16:00:00

...

issue MZ-n

...

current_time

...

Jira issue created

...

issue MZ-5

...

2010.02.01 17:00:00

...

Jira issue untouched

ADD_UPDATE_DELETE Option

Using ADD_UPDATE_DELETE configuration option in the right side (Jira issue), after the synchronization, the system hold these values:

...

Left element (EA usecases)

...

Last update

...

Right element (JIRA issues)

...

Last update

...

Comment

...

usecase UC001

...

2010.02.01 10:00:00

...

issue MZ-1

...

current_time

...

Jira issue fields updated

...

usecase UC002

...

2010.02.01 12:00:00

...

issue MZ-2

...

current_time

...

Jira issue fields updated

...

usecase UC003

...

2010.02.01 14:00:00

...

issue MZ-3

...

current_time

...

Jira issue fields updated

...

usecase UC004

...

2010.02.01 16:00:00

...

issue MZ-n

...

current_time

...

Jira issue created

...

issue MZ-5

...

2010.02.01 17:00:00

...

Jira issue untouched

Options Resume