...
Left element (EA usecases) | Last update | Right element (JIRA issues) | Last update | Comment |
|---|---|---|---|---|
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 | Jira issue untouched |
usecase UC001 | 2010.02.01 10:00:00 | issue MZ-1 | 2010.02.01 09:00:00 | |
usecase UC002 | 2010.02.01 12:00:00 | issue MZ-2 | 2010.02.01 11:00:00 | |
usecase UC003 | 2010.02.01 14:00:00 | issue MZ-3 | 2010.02.01 15:00:00 | usecase UC004 | 2010.02.01 16:00:00 | issue MZ-5 | 2010.02.01 17: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:
usecase 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 | Jira issue untouched 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 | Jira issue untouched Usecase and issue are connected, and jira issue information is more recent | |||
usecase UC004 | 2010.02.01 16:00:00 | issue MZ-n | current_time | Jira issue created | issue A usecase exist, but not an equivalent issue | ||
issue MZ-5 | 2010.02.01 17: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 | A jira issue exist, but not an equivalent usecase | |||||
| issue MZ-6 | 2010.02.01 1219: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
...
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) | 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
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 | |
x | issue MZ-5 6 | None | None | issue MZ-5 6 deleted | issue MZ-5 6 deleted |