# Jira integrations

*9 integrations*

**In short:** 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.

## What connects to Jira

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](https://seamless.engineering/integrations/zendesk-jira/), Freshdesk or Freshservice ticket, or a [ServiceNow](https://seamless.engineering/integrations/servicenow-jira/) 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](https://seamless.engineering/integrations/salesforce-jira/), 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](https://seamless.engineering/integrations/jira-slack/), threaded per issue, with replies coming back as comments.

## Where Jira integrations break

- **Status is a transition, not a field.** Jira only allows the transitions its workflow defines from the current status, some behind screens with required fields. A sync that writes status values fails or leaves issues stuck, and every project can define its own workflow.
- **Echo loops.** A write into Jira fires a Jira webhook, which would write back into the other system, which fires its own event. Without an origin marker and suppression of the pipeline's own events, one update ping-pongs forever.
- **Atlassian Document Format.** Jira Cloud stores rich text as ADF. Service desk HTML, Notion blocks and Slack mrkdwn all need a real conversion, or formatting, mentions and code blocks arrive mangled.
- **Custom field IDs are per instance.** Fields are `customfield_10042` and carry different numbers across Jira sites and sandboxes, so they are mapped by ID, never by label.
- **Identity and limits.** Jira Cloud identifies people by accountId and may hide email, and it enforces cost-based rate limits answered with 429. Assignee mapping needs a real lookup, and bursts need queuing and backoff.

## All Jira integrations

### Support ↔ ITSM & Dev

- [Zendesk ↔ Jira](https://seamless.engineering/integrations/zendesk-jira/): Zendesk Jira integration
- [Freshdesk ↔ Jira](https://seamless.engineering/integrations/freshdesk-jira/): Freshdesk Jira integration
- [ServiceNow ↔ Jira](https://seamless.engineering/integrations/servicenow-jira/): ServiceNow Jira integration
- [Freshservice ↔ Jira](https://seamless.engineering/integrations/freshservice-jira/): Freshservice Jira integration
- [Jira ↔ Slack](https://seamless.engineering/integrations/jira-slack/): Jira Slack integration
- [Salesforce ↔ Jira](https://seamless.engineering/integrations/salesforce-jira/): Salesforce Jira integration

### Collaboration ↔ Ops

- [Asana ↔ Jira](https://seamless.engineering/integrations/asana-jira/): Asana Jira integration
- [Notion ↔ Jira](https://seamless.engineering/integrations/notion-jira/): Notion Jira integration
- [Smartsheet ↔ Jira](https://seamless.engineering/integrations/smartsheet-jira/): Smartsheet Jira integration

## Jira API changelog

- [Jira Cloud API changelog](https://seamless.engineering/api-changelog/jira/): 2 breaking changes and 11 deprecations in the last 90 days

## Request a scoping call

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.

- Email: hello@seamless.engineering
- Contact form: https://seamless.engineering/#contact