# Auto-Push on Issue Update
Auto-Push is the event-driven sync that makes SyncBridge useful without any manual effort. When a Jira issue in a bound project is updated, the connector automatically pushes the mapped field values to the linked Salesforce record — no one has to click anything.
How It Works
The connector registers a Forge trigger (avi:jira:updated:issue) that fires whenever a Jira issue is updated in any project. On each fire:
The trigger checks whether the issue's project has any bindings.
For each binding, it checks whether the issue type matches an entity mapping.
If matched, it checks whether any Salesforce records are linked to this issue via that binding.
For each linked record, if Auto-Push is not disabled, it applies the field mappings (Jira → Salesforce direction) and sends a PATCH to the Salesforce REST API.
The sync status and timestamp on the association are updated.
Auto-Push checkbox enabled in Sync Settings
Association card showing sync status updated by auto-push after an issue edit
Enabling and Disabling Auto-Push
Auto-Push is controlled per binding in Sync Settings. It is enabled by default for new bindings.
Timing
The trigger fires within seconds of the Jira issue being saved. The Salesforce API call happens asynchronously on Forge's infrastructure. In normal conditions, the Salesforce record is updated within 3–10 seconds of the Jira change.
What Does Not Trigger Auto-Push
Jira comment additions (comments do not fire avi:jira:updated:issue)
Jira issue creation — creation fires avi:jira:created:issue, which drives Auto-Create, not auto-push
Jira issues with no Salesforce records linked
Issues in projects with no bindings