Connecting Jira Cloud with Unito? Here's what you can expect from this integration.
In this article:
What Unito syncs from Jira Cloud
Unito syncs issues from Jira Cloud projects by linking individual fields from these issues to items in other tools (e.g., Asana tasks, Salesforce cases, ServiceNow records).
This article applies to Unito users with an enterprise plan for a Unito workspace created after July 23rd, 2025. If you don't meet these criteria, you'll want to consult this guide, instead.
Supported fields for Jira Cloud issues
Unito supports the following fields and rules for Jira Cloud. If you don't see a field you need in this list, reach out to us. We may be able to add it to your workspace if it's available in Jira's API.
Quick definitions:
- One-way: Changes in this field can be synced to the tool it's integrated with, but changes in the other can't be synced back.
- Two-way: Changes to this field will be synced to the tool it’s integrated with, and changes in the other tool will be synced back.
- Rules: This field can be used to build rules.
| Issue Fields | One-Way | Two-Way | Rules |
| Affected version | ✔ | ✔ | |
| Assignee | ✔ | ✔ | ✔ |
| Attachment | ✔ | ||
| Comment | ✔ | ✔ | |
| Component | ✔ | ✔ | ✔ |
|
Date picker (custom field)*
|
✔ | ✔ | |
|
Date time (custom field)*
|
✔ | ✔ | |
| Description | ✔ | ✔ | |
| Due date | ✔ | ✔ | |
| Epic | ✔ | ✔ | ✔ |
| Fix version | ✔ | ✔ | ✔ |
|
Float (custom field)*
|
✔ | ✔ | |
| Issue id | ✔ | ||
| Issue number | ✔ | ||
| Issue status | ✔ | ✔ | ✔ |
| Issue type | ✔ | ✔ | ✔ |
| Label | ✔ | ✔ | ✔ |
| Link to issue | ✔ | ||
|
Multiple checkbox (custom field)*
|
✔ | ✔ | |
|
Multiple select list (custom field)*
|
✔ | ✔ | ✔ |
|
Multiple user picker (custom field)*
|
✔ | ✔ | ✔ |
|
Original time estimate
|
✔ | ||
| Priority | ✔ | ✔ | |
| Project name | ✔ | ||
|
Radio button (custom field)*
|
✔ | ✔ | |
|
Remaining estimated duration
|
✔ | ||
| Reporter | ✔ | ✔ | |
| Resolution | ✔ | ✔ | |
| Security Level | ✔ | ✔ | ✔ |
|
Single select list (custom field)*
|
✔ | ✔ | ✔ |
| Sprint | ✔ | ✔ | ✔ |
| Story point estimate | ✔ | ✔ | |
| Subtask | ✔ | ✔ | |
| Summary | ✔ | ✔ | |
|
Text field (custom field)*
|
✔ | ✔ | |
|
Textarea (custom field)*
|
✔ | ✔ | |
| Time spent | ✔ | ✔ | |
|
Url (custom field)*
|
✔ | ✔ | |
|
User picker (custom field)*
|
✔ | ✔ |
*Custom fields.
Additional features
Unito's Jira Cloud integration also supports the following features:
- Rich text: All rich text type fields are supported by default.
- Multi-project functionality: When you build a Unito flow with Jira Cloud, your flow will sync issues from a single Jira project by default. If you want to sync issues from multiple projects in a single flow, reach out to your sales representative.
- Item types: When building a Unito flow with Jira, you can choose between two subtask configurations.
- Issue (Hierarchy) which maintains the hierarchy between issues and subtasks. Epics will sync separately.
- Issue (Epic Hierarchy) which makes epics the main work item you sync, with issues as sub-items, and subtasks as sub-items under issues.
- Attachments: Unito can copy attachments to and from Jira issues, meaning the whole file will be available in any synced work item as long as it's mapped to an attachment field in your other tool. You can also stream attachments to the description footer of the other tool, adding a clickable link for anyone in the other tool to view it without logging in to Jira.
Unsupported features for Jira Cloud
Need something this integration doesn't support yet? We can help you work around many of these limitations. Meet with us to find out how.
- Rich text in comments: Rich text in comments isn't supported by default, but you can activate this by adding this code snippet in your flow's manual options
{ "richTextComments": true } - @ mentions in comments: These aren't supported.
- Creating Jira projects from Unito: This isn't currently supported.
- Unsupported Jira fields: Below is a list of Jira fields that aren't currently supported by this integration.
- Assignee custom field
- Time tracking
- Story point estimate
- Multi-select dropdown custom field
- Organizations
- Checkbox custom field
- Label custom field
- Voted
- Linked issues
- Dependencies and mandatory fields: If your Jira issues have mandatory fields, they may not sync over properly to other tools, or be created at all. To achieve smooth functionality, we recommend that you avoid mandatory fields and dependencies in your Jira projects. This includes linked issues, which aren't supported by this integration.
- Sprints: Unito can only sync Jira sprints that meet the three following requirements: they have to be active, they have to be associated with a board, and that board has to be associated with a project.
- Permissions: You need administrator permissions to connect your Jira account to Unito. Once the account is connected, you only need project-level admin permissions to create a flow. You can learn more about required Jira permissions here.
- Syncing subtasks as parent tasks: This isn't currently supported. Subtasks can only be synced with subasks in other tools.
- Custom issue types for subitems: While this field is supported for parent issues, it isn't supported for sub-items.
- Edited comments: When you edit comments in Jira, these edits won't be synced over to other projects or other tools. That's because Unito only syncs new comments, not any edits to existing comments.
- (Jira Server) Old databases: If the installation is using an old database (e.g. MySQL < 8.0), we do not support adding Description footer on tasks.
- Jira URL: If the Jira URL contains ‘.atlassian.net’ it means that it’s considered “Cloud”. If it doesn’t have it, then it’ll be considered as “Server”.