Exalated
For this discussion, we imagine two JIRAs: JIRA A (https://a.com) and JIRA B (https://b.com). Synchronization occurs to B via relation "AtoB":
Whenever an issue A-1 (id 10000, on JIRA A) has been successfully exalated (meaning all the exalate set up processes have been finalized on both the nodes) to an issue B-1 (id 20000, on JIRA B), the following takes place:
- an EXALATED event is fired on JIRA A (when the exalate activities for the first sync have been completed, the response from JIRA B has been received and processed)
- an EXALATED event is fired on JIRA B (when the exalate activities for the first sync have been completed, the request from JIRA A has been processed and the response to JIRA A has been sent successfully)
Parameters available when receiving and event
You can subscribe to all the "Issue Event"s and then, using the method below, you can get the following event context values:
public Map<String, Object> getParams()
|
|
Parameter Key | Parameter Value Constraints | Parameter Value Description | Parameter Value Java Type |
|---|---|---|---|---|
| 1 |
LOCAL_ISSUE_ID |
Non-null | The id of the local issue been exalated. | java.lang.Long |
| 2 |
LOCAL_ISSUE_URN |
Non-null | The key of the local issue been exalated. | java.lang.String |
| 3 | REMOTE_ISSUE_ID | Non-null | The id of the remote issue been exalated. | java.lang.Long |
| 4 | REMOTE_ISSUE_URN | Non-null | The key of the remote issue been exalated. | java.lang.String |
| 5 | RELATION_NAME | Non-null | The name of the relation under which the issues have been exalated. | java.lang.String |
| 6 | INSTANCE_NAME | Non-null | The name of the remote Instance, the remote issue is on. | java.lang.String |
| 7 | INSTANCE_URL | Non-null | The url of the remote Instance, the remote issue is on. | java.lang.String |
| 8 | EXALATE_JIRA_EVENT_TYPE | "EXALATED" (constant) | The identifying property to distinguish EXALATED JIRA event from other IssueRelatedEvent. | java.lang.String |
Example
In the example of JIRA A to B sync:
on JIRA A an exalated event's parameters would look as follows:
| Parameter Key | Parameter Value |
|---|---|
|
LOCAL_ISSUE_ID |
10000L |
|
LOCAL_ISSUE_URN |
"A-1" |
| REMOTE_ISSUE_ID | 20000L |
| REMOTE_ISSUE_URN | "B-1" |
| RELATION_NAME | AtoB |
| INSTANCE_NAME | B |
| INSTANCE_URL | https://b.com |
| EXALATE_JIRA_EVENT_TYPE | "EXALATED" |
on JIRA B an exalated event's parameters would look as follows:
| Parameter Key | Parameter Value |
|---|---|
|
LOCAL_ISSUE_ID |
20000L |
|
LOCAL_ISSUE_URN |
"B-1" |
| REMOTE_ISSUE_ID | 10000L |
| REMOTE_ISSUE_URN | "A-1" |
| RELATION_NAME | AtoB |
| INSTANCE_NAME | A |
| INSTANCE_URL | https://a.com |
| EXALATE_JIRA_EVENT_TYPE | "EXALATED" |
Other events
Other events are also declared in the interface but not yet implemented:
- Unexalated
- Deleted
- Updated