Sage X3 and Jira integration

What moves between them

The flow is one-way: from Sage X3 into Jira. Purchase orders and supplier invoices from Sage X3 are polled on a schedule and created as Jira issues in a designated project, with custom fields capturing vendor name, order date, delivery date, line items, and amounts. As purchase orders are updated or fulfilled in Sage X3, the corresponding Jira issues are kept in sync. Jira issues remain the source of truth for task comments, attachments, and status notes; no data flows back into Sage X3 financials.

How ml-connector handles it

ml-connector stores the Sage X3 credentials encrypted and polls the GraphQL or REST endpoint for new and modified purchase orders and invoices using the updatedDate field to detect changes since the last sync. For each record, it extracts the vendor, order total, line items, and delivery date, then creates or updates a matching Jira issue in the target project. Supplier names are looked up once and cached to avoid repeated Sage X3 queries. Custom field IDs are resolved at setup time since they vary per Jira instance. Sage X3 access tokens expire in 5 minutes, so ml-connector refreshes them transparently before each request. If the target Jira project does not exist or a custom field is misconfigured, the sync logs the error and retries on the next cycle, preserving every record in the audit trail for manual replay once the issue is fixed.

A real-world example

A mid-sized manufacturer runs Sage X3 for procurement and materials management, and uses Jira for project and operations tracking. Before the integration, purchase orders entered in Sage X3 were manually forwarded to the operations team via email or spreadsheet, and delivery date changes required manual updates to Jira subtasks. The procurement team and operations team operated in separate systems with no visibility into each other's data. With Sage X3 and Jira connected, every new purchase order appears as a Jira issue within seconds, tagged with vendor name and expected delivery date, and the team can comment and add attachments right in Jira. Changes to delivery dates and amounts in Sage X3 sync back to Jira, so the operations team always sees the current state without checking multiple systems.

What you can do

• •Poll Sage X3 purchase orders and supplier invoices and create Jira issues in your designated project with vendor and cost details.
• •Map Sage X3 suppliers, order dates, delivery dates, and line-item amounts to Jira custom fields for full visibility.
• •Sync updates to purchase orders and invoices from Sage X3 back to Jira issues to keep delivery dates and amounts current.
• •Handle Sage X3 OAuth2 and Basic auth, token refresh, and the unique server URL per customer instance.
• •Detect changes using Sage X3 updatedDate fields and poll on a schedule you control, with full audit trail and error replay.

Questions

Does data flow in both directions between Sage X3 and Jira?

No, the flow is one-way from Sage X3 into Jira. Purchase orders and supplier invoices from Sage X3 are synced into Jira issues for visibility and task tracking. Jira issues remain the source of truth for comments and attachments; no financial updates flow back into Sage X3.

How does ml-connector handle Sage X3's unique server URLs and lack of webhooks?

ml-connector accepts the full Sage X3 server URL and folder name per customer since there is no shared hostname. Because Sage X3 has no native webhooks, ml-connector polls on a schedule tied to your procurement calendar, using the updatedDate field to detect which records have changed since the last sync.

What happens if a Sage X3 access token expires or a Jira custom field is missing?

Sage X3 tokens expire every 5 minutes, so ml-connector refreshes them transparently before each request. If a Jira custom field is misconfigured or the project does not exist, the sync logs the error and retries on the next cycle, preserving every record in the audit trail for manual replay once you fix the issue.