| CREATECreate | JIRA events - specifies when synchronization process will begin. It requests to create issue in corresponding remote Context (remote JIRA instance). |
| UPDATE | JIRA events - specifies when to send update request to (previously created) corresponding remote JIRA issue. |
| DELETE | JIRA events - specifies when to send information about synchronization brake. It will not delete remote issue. It will just delete information about remote issue. |
when remote create issue should be triggered. It does not always have to be CREATE_ISSUE. You may use a workflow that at certain point triggers some custom event. That event can create remote issue too. | |
| Update | JIRA events to trigger update messages.
|
| Comments | See Comments & Attachments |
| Attachments | See Comments & Attachments |
| Workflow Mapping | On contract you can select corresponding workflow mapping scheme. From now on workflow will synchronize. |
Trigger section is split in two: local and remote triggers. (It will be up to date after configuration is synchronized. It is done automatically in the background. May have some delay. You can force it by pressing "Synchronize configuration" at Connection.)
So you may know what to expect from remote JIRA.
You can trigger remote issue creationTriggers can be:
- Automatic (specify CREATE eventsEvents)
- Manual (Create Remote Action)
JIRA Events can be thrown in different scenarios. The most common are built-in event triggered by system and workflow events triggered by transitions. You can also trigger events programmatically (add-ons or groovy scripts).
| Info |
|---|
Mind that issue must met JQL constraints to make IssueSYNC follow your specified Eventslisten for events.
|
