Limitations of Unito's Jira Service Management Integration

Here's a breakdown of what Unito's integration for this tool can't do yet — and a few other considerations.

Unito's Jira Service Management integration is designed to get crucial data out of your projects and into other tools. You've seen what Unito can do for Jira Service Management users, so this article will cover what it can't do — yet.

What this article covers:

• Unsupported fields
• Mapping limitations
• Limitations for Unito accounts created after April 29th 2025
• Other considerations

Unsupported fields

• Multi-line text fields
• Checkboxes
• Time-tracking
• Story point estimate
• Voted

Mapping limitations

• Mapping Reporter to other assignee fields: Not supported currently.
• Fix version: Currently, this can only be mapped to Text custom fields, not dropdowns or lists.

Limitations for Unito accounts created after April 29th 2025

Unito workspaces created after this date are using a new version of the Jira connector, which have some additional limitations:

• Creating Jira projects from Unito isn't supported.
• @mentions in comments can't be synced with Unito.
• Mapping Jira ID to task titles isn't supported.
• Syncing parent tasks as epics isn't supported.

Other considerations

• Administrator permissions: You need administrator permissions to connect your Jira Service Management account to Unito. Once the account is connected, you only need project-level admin permissions to create a flow.
• Sprints in next-gen projects: Not currently supported.