Table of Contents
Triggers based on events
First you need to define your events that trigger issues synchronization.
| CREATE | 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. |
| Info |
|---|
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). |
JQL filtering
Mind that issue must met JQL constraints to make IssueSYNC follow your specified Events. See Synchronization Scheme
No JQL means - all issues will be synchronized.
Create On Demand (Create Remote Action)
Create On Demand allows you to make a decision per each issue whether you want to synchronize it or not.
You need to meet following conditions to see this button 
- Issue is in Synchronization Scheme
- No remote issue is created yet
- Permission for this action are set to your user Administration → IssueSYNC → Configuration → General
