Integrating Jira means connecting the engineering backlog to the systems where work is requested, planned or discussed: service desks escalate into it, planning tools and CRMs push work in, and Slack carries its events out. What breaks is almost always the same: statuses that change only through workflow transitions, rich text in Atlassian Document Format, per-instance custom field IDs, and two-way syncs that echo their own updates.
Jira is where engineering work is tracked, and most of its integrations exist because that work starts somewhere else.
Support and service desks are the largest group. A Zendesk, Freshdesk or Freshservice ticket, or a ServiceNow incident, escalates into a Jira issue, and status, comments and the resolution flow back to the agent and the requester. CRM teams do the same from Salesforce, carrying account, tier and contract value into the issue so engineering can prioritise. Business and PMO teams plan in Asana, Notion or Smartsheet and keep those plans in step with the backlog. In the other direction, Jira events go out to Slack, threaded per issue, with replies coming back as comments.
customfield_10042 and carry different numbers across Jira sites and sandboxes, so they are mapped by ID, never by label.Connecting Jira to something not listed here? Tell us which systems are involved and what data has to move. Fixed-price scoping quote within 48 hours.