What to see and do on Customer and Contact
Once table and field mapping is configured, both the Customer Card and Contact Card get a Jira Integration section.
Enabling synchronization requires DYCE Connector for Jira & Jira Service Management to be activated. See the DYCE Activation Status page if synchronization cannot be enabled for this reason.
Customer card
| Field | Meaning |
|---|---|
| Enable Jira Sync | Enables synchronization of this customer as a Jira Organization |
| Jira Sync Status | Status of the latest synchronization message; select it to open that message |
| Last Jira Sync | Date and time of the last synchronization attempt |
| Jira Organization ID | ID of the corresponding organization in Jira, once synced |
| Jira Combined Name | The combined name sent to Jira, if enabled on the table mapping |
Actions: Manual Sync queues an immediate synchronization message for this customer; View Messages opens the message queue filtered to this customer.
Contact card
| Field | Meaning |
|---|---|
| Enable Jira Sync | Enables synchronization of this contact as a Jira Customer (Person type contacts only) |
| Jira Customer ID | ID of the corresponding customer in Jira, once synced |
| Jira Sync Status | Status of the latest synchronization message; select it to open that message |
| Last Jira Sync | Date and time of the last synchronization attempt |
| Jira Combined Name | The combined name sent to Jira, if enabled on the table mapping |
Actions: Sync to Jira queues an immediate synchronization message for this contact; View Message Queue opens the message queue filtered to this contact.
Enabling and disabling synchronization
Turning on Enable Jira Sync validates that the record can actually be synced and reports a clear error otherwise, for example a missing enabled table mapping, an unauthorized OAuth2 setup, or no enabled field mappings. Once enabled, the record status changes to Pending and the first synchronization message is queued.
Turning Enable Jira Sync back off does not delete the record in Jira. If unprocessed messages still exist for the record, disabling asks for confirmation and cancels those pending messages.