Learn the best use cases for a Zendesk-Jira integration, what fields are synced between the two tools, and your customization options.
In this article:
Supported fields for Zendesk and Jira
Zendesk | Jira | |
Title | ←→ | Title |
Description | ←→ | Description |
Internal notes | ←→ | Comments |
Status | ←→ | Status |
Priority | ←→ | Priority |
Assignee | ←→ | Assignee |
Tags | ←→ | Labels |
Task due date | ←→ | Due date |
Description footer | ← | Attachments |
Link to ticket | → | Description footer |
Description footer | ← | Link to issue |
Ticket type | → | Issue type |
Submitter | → | Reporter |
Ticket number | → | Description footer |
Description footer | ← | Issue number |
Description footer | ← | Epic |
Description footer | ← | Start date |
Description footer | ← | Sprint |
Description footer | ← | Sprint start date |
Description footer | ← | Sprint end date |
Description footer | ← | Original estimated duration |
Description footer | ← | Remaining estimated duration |
Description footer | ← | Time spent |
Description footer | ← | Project name |
Description footer | ← | Components |
Description footer | ← | Affected versions |
Description footer | ← | Fix versions |
Group name | → | Description footer |
Note: After the initial sync, the Zendesk ticket description cannot be updated due to its read-only first comment nature. Any changes on the synced task description or fields of the description footer cannot be reflected in Zendesk.
Customization options for Zendesk + Jira integrations
- Syncing public Zendesk comments: By default, only internal notes will sync but you can also sync Zendesk public replies.
- Default type for new Jira issues: Unito lets you choose which issue type should be created in Jira each time a new ticket is synced from Zendesk.
- Prefix Zendesk ticket title with Jira issue number: Unito doesn't sync the ticket number from Zendesk to Jira by default but you can enable numbers syncing to task titles in your sync settings under the more options tab.