Looking to add Jira to your workflow? Here's what you can expect from our integration.
Which version of Jira is this integration compatible with?
Unito is compatible with Jira Cloud and on-premise versions of Jira. You can use Unito with Jira Server version 6.7.7 and up, and Jira Data Center.
Jira offers both classic and next-generation projects. Both types of projects are compatible with Unito.
Synced fields
Here are the fields you can currently sync with Jira, whether they can be used in two-way flows, as well as whether you can use them in rules or not.
Most fields can be synced both ways. This means changes in one tool will affect the other and vice-versa. You can also edit a flow (or a specific field mapping) so that changes only go from one tool to the other and not back.
Custom fields and other options
Our Jira integration supports a number of custom fields and other customization settings.
Custom fields
The custom fields supported by this integration are Date, Number, Single-select dropdown, and Text fields. You can also build rules with the Single-select dropdown and Text fields.
Subtasks
Jira subtasks can be synced with other tools that have subtasks, such as Asana.
Issue type
When a Jira issue is created to match a task in another tool — like a Trello card — you can determine which issue type will be created by default.
Attachment streaming
You can stream Jira attachments, meaning anyone with the link can view the files without logging into Jira.
Issue numbers as prefixes
You can have a Jira issue number automatically be added as a prefix in the work item it's synced to outside of Jira.
Rich text formatting
Unito translates rich text formatting between tools, keeping your task descriptions fully synced. However, there are some formatting options that are only partially translated from one platform to the other, while a few options are not supported entirely. Here is a list of formatting options that are preserved when syncing Jira issues:
-
Headings (levels 1 through 6)
-
Bold
-
Underline
-
Italic
-
Strikethrough
-
Hyperlinks
-
Unordered Lists
-
Tables
Limitations and other things to keep in mind
We’re constantly looking to better support Jira’s growing list of features, fields, and use-cases. Here are a few common limitations you should be aware of:
-
Sprint value mapping is not supported in Next-Gen projects
-
Custom field type assignee
-
Time Tracking field
-
Story point estimated field
-
Custom field: multi-select dropdowns (on the roadmap!)
-
Syncing Initiatives as parent tasks (but we can sync the content inside the initiatives)
-
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.
We're constantly working to improve our integrations. Contact us if you’d like to see another Jira field or use-case added to the roadmap!
Things to keep in mind
Here are a few things to keep in mind:
-
We need Admin permissions, application link setup, and public email visibility on Jira settings for authentication. If you use an embedded version of our Jira integration, you can bypass the application link setup.
-
In order for on-premise Jira accounts to connect to Unito, it needs to be accessible via the internet. If that isn't the case, please read our guide to set this up, or contact us if you’re not sure how to proceed!
-
Jira’s Time spent field is incremental and as such can only increase in value. The field it is mapped to will be able to update it as long as its value is greater than the current time spent in Jira. If the value in the field is less than Jira’s Time spent, it will not be updated.
Necessary permissions
In order to sync your Jira projects, you'll need a mix of global and project-specific permissions, from login permissions to issue and comment permissions. You can find the full list of user permissions here.
Note that 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.
If you get stuck on setting up permissions schemes in Jira, you can find a guide here.
OAuth Scopes
Read
View, browse, and read information from Jira.
Write
Create or edit content in Jira, but not delete content.
Using Jira with OAuth2
Jira's OAuth2 allows you to connect Unito with Jira without being an administrator. It's a smoother, easier way to start creating flows without worrying about the level of permissions you have or getting authorization tokens. That said, there are a few things to keep in mind if you use OAuth2:
-
Limited Webhooks: Webhooks are how Unito keeps lightning-fast flow speeds. With OAuth2, the number of Webhooks is limited, meaning you can have live changes for up to five Jira projects. If you're syncing more projects than that, they will be updated every five minutes or so.
-
Email address access: With OAuth2, Unito won't have access to the email addresses of all Jira users in your workspace. That means your Jira flows will match users by full name rather than email. This might create some mismatches.
-
Attachment access: Jira offers enhanced security when connecting with OAuth 2, and this includes restricted access to attachments. That means linked attachments won't be accessible. Only streamed attachments will work with OAuth 2. Here's more information on the difference between them.
Note that OAuth2 is only available if you've never connected Jira to your Unito workspace. You won't be able to disconnect Jira from your workspace to then reconnect it using OAuth2. This is a limitation from Jira's API.
Is there an embedded version of this integration?
Unito can be used as a standalone app from our website or, with some integrations, be accessed from within the tool you're most comfortable in. These are called embedded integrations. Jira is one of these integrations. Here is a list of the different tools you can use with our Jira integration, without leaving the tool:
-
Jira Cloud
-
monday.com
-
Trello
-
Wrike