Jira Data Center
      Back to home
      1. Help Center
      2. Atlassian Jira Integration Docs
      3. Jira Data Center

      An Overview of Unito's Jira Data Center Integration

      Ready to start syncing Jira issues to your other tools? Here's everything you need to know.

      What does this article cover?

      What does Unito sync from Jira Data Center?

      Unito syncs Jira issues from your Jira projects.

      If you'd like to sync issues from multiple Jira projects within the same workspace, you can create one flow for the first project, then duplicate that flow and edit it to sync issues from any additional projects.

      Which Jira Data Center fields can Unito sync?

      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 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 ✔ ✔  
      Single select list (custom field)
      		 ✔ ✔ ✔
      Sprint ✔ ✔ ✔
      Sprint end date ✔    
      Sprint start date ✔    
      Story point estimate ✔ ✔  
      Subtask ✔ ✔  
      Summary ✔ ✔  
      Text field (custom field)
      		 ✔ ✔  
      Textarea (custom field)
      		 ✔ ✔  
      Time spent ✔ ✔  
      Url (custom field)
      		 ✔ ✔  
      User picker (custom field)
      		 ✔ ✔  

      *Jira Data Center attachments are supported through streamed attachments, which make the attachment visible in both tools without jumping between Jira projects. Attachment support for Jira Data Center is only available for Pro, Business, or Enterprise plans.

      How to connect Jira Data Center with Unito

      Before you can sync Jira issues out of your projects, you'll need to connect your Jira Data Center with Unito. There are three ways to do this.

      Authorizing with an API token

      API tokens can be generated in Jira and added to Unito to create a secure connection. Here's how it works.

      image (6)

      Authorizing with a username and password

      The simplest way to connect Jira with Unito is to use your Jira credentials in Unito. Just use the same email and password that you use to log in to Jira.

      user password edit

      Authorizing with OAuth

      With OAuth, you can set up a secure connection between Jira and Unito.Here's the basic rundown.

      image (9)(1)

      And now for the detailed steps-by-step. Once in Jira, you'll want to open the Jira admin settings through the gear in the top-right, then hit Application links.

      Jira oauth 2 edit

      From there, hit Create link.

      Jira oauth 2 edit(1)

      You'll then see this screen. Make sure to select External application and Incoming before hitting Continue.

      image (9)(2)

      You'll then get a Client ID and a Client secret. Just copy and paste these into Unito, and you'll have successfully connected your Jira Data Center account with Unito!

      Jira oauth 3 edit

      Limitations and other considerations

      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:

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

      • Sprint value mapping is not supported in Next-Gen projects

      • These fields aren't supported: custom field type assignee, time tracking field, 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.
      • Unito's Jira integration doesn't support Linked Issues.

      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!