An Overview of Unito's Jira Server Integration

Connect a Jira Server instance to your favorite tools for seamless collaboration and efficient project management.

In this article:

Note: On May 1, 2024 Atlassian announced that Jira Work Management and Jira Software would be combined into a single tool simply known as "Jira". 

Unito supports this unified Jira experience, and the integration process remains the same.

Browse similar overviews of Jira Service Management and Jira Data Center.

Unito can sync issues with work items in other tools through the Unito app for Jira or directly through Unito's standalone sync platform. By creating a Unito flow, you'll be able to sync Jira issues or tasks with automated updates based on rules set by you.

Each Unito flow is comprised of the following steps:

What Jira Server Versions Does Unito Support?

Unito supports Jira Server versions 6.7.7 and newer. While Atlassian has announced the end of support for Jira Server in February 2024, you can still leverage Unito to integrate your existing Jira Server instance with other tools.

Supported Jira Server issue fields in Unito

The table below lists out all the fields you can sync with our Jira integration, as well as which fields can be used in rules.

Quick definitions:

    • One-Way: Changes to the Jira issue field will appear in the other synced field but not vice versa.
    • Two-Way: Changes to either synced field will appear in the other.
    • Rules: This Jira issue field can be used as a trigger in your rules to filter work items from syncing with Unito.
Issue Field One-Way Sync Two-Way Sync
Filterable (Rules)
Affected Version -
Assignee
Attachment - -
Comment -
Component
Date Picker (custom) -
Date/Time (custom) -
Description -
Due Date -
Epic
Fix Version
Float (custom) -
Issue ID - -
Issue Number - -
Issue Status
Issue Type
Label
Link to Issue - -
Multi-Checkbox (custom) -
Multi-Select (custom)
Multi-User (custom)
Original Time Estimate - -
Priority -
Project Name - -
Radio Button (custom) -
Remaining Estimate - -
Reporter -
Resolution -
Security Level
Single-Select (custom)
Sprint
Sprint End Date - -
Sprint Start Date - -
Story Point Estimate -
Subtask -
Summary -
Text Field (custom) -
Textarea (custom) -
Time Spent -
URL (custom) -
User Picker (custom) -

Custom fields are only available with certain plans. Visit Unito's pricing page for more information.

What counts as an item in sync?

For Jira, Unito counts issues, tasks and subtasks as items in sync. So if you sync a Jira issue that has a subtask, Unito will count this as four items in sync (2 in your Jira project, 2 in your other connected project).

Ready to get started? Browse our list of Jira-specific step-by-step walkthroughs to set up your first no-code 2-way Jira flow with Unito.

How to connect Jira Server to Unito

Unito offers multiple ways to connect your Jira Server instance, each with its own advantages. In all cases though, you'll need to create an application link in your Jira Server instance.

Jira Server Screenshot Advanced Settings

If you're interested in further customizing your setup, you can read about advanced configuration options for Jira Server.

Connecting via OAuth

OAuth is an easier, more secure way to start creating flows without worrying about the level of permissions you have or getting authorization tokens. But there are limitations:

  • Limited webhooks: Jira Server's OAuth implementation may restrict the number of webhooks available for real-time updates. If you exceed this limit, some projects might sync less frequently.
  • Email access: Unito might not have access to all Jira user email addresses, potentially leading to mismatched users in flows. That means your Jira flows will match users by full name rather than email. This might create some mismatches.
  • Attachment access: Only streamed attachments are supported with OAuth in Jira Server. Here's more information on the difference between them.

Other Connection Options:

  • Username and Password: This classic authentication method is straightforward, but requires entering your Jira credentials directly in Unito.
  • API Token: Similar to a password, but provides more granular control over permissions and can be revoked if needed. Here's an Atlassian guide to API tokens in Jira.

Custom fields and other options for Jira users

Unito's 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 added as a prefix in the work item it's synced to outside of Jira Server.

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

Watch a demo video

Here's a demo showing one of our product specialists syncing data between Jira and ServiceNow:

Follow along with this step-by-step Jira ServiceNow tutorial.

OAuth Scopes

Read

View, browse, and read information from Jira.

Write

Create or edit content in Jira, but not delete content.

Limitations of Unito's Jira Server integration

    • If the installation is using an old database (e.g. MySQL < 8.0), we do not support adding Description footer on tasks.
    • Unito only supports Jira versions supported: 6.7.7 and up. 
    • 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”.
  • 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.
  • These fields are not supported: custom field type assignee, time tracking field, Linked Issues, story point estimated field, multi-select dropdown custom fields.

  • 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.

  • 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.

Related articles

Start syncing Jira Server to your other apps and tools

Here are several tool-specific guides and resources to help you connect Jira projects with other apps and tools supported by Unito:


Got feedback? Submit a Unito feature request to let us know what you'd like to see in the next update to our Jira integration.