Events

Create You can choose when/on which Jira events trigger remote issue creation. Most common event for synchronization setup is ISSUE_CREATED - when you create an issue in local Jira instance, remote one will be created as well.

You may use a workflow that at certain transition triggers some event. That event can create remote issue too.

Update You can choose when/on which Jira events trigger remote issue update. Most common events for synchronization setup are ISSUE_UPDATED and ISSUE_COMMENTED.

!Issue must be created first to make update happen! If it is not, there will be no synchronization.

Comments See Comments & Attachments

Attachments See Comments & Attachments

Workflow Mapping You can select corresponding workflow mapping. From now on workflow will synchronize, so when you make a transition in local Jira instance, remote issue will be transitioned as well (corresponding transition configured in workflow mapping scheme in remote Jira instance)

See Workflow Synchronization

Local vs remote

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.

Automated vs manual

Triggers can be:

• Automatic (Events)
• Manual (Create Remote Action)

Jira Events can be thrown in different scenarios. The most common are built-in events triggered by system and workflow events triggered by transitions. You can also use programmed events (add-ons or groovy scripts).

Constraints

Mind that issue must met JQL constraints to make IssueSYNC listen for events.