Join us at Elevate✨ Our virtual conference hits screens Dec 14thJoin us at Elevate conference✨ Tune in Dec 14thRegister now

What can we help you with?

How to import from Jira Server


With a couple of clicks, you can easily import your work from Jira Server into!


Connect your account

To begin the import, click on "Add" at the top of your left pane, then select "Import data" and then "Jira server".





You will then see a page prompting you to enter your Jira Server account information in order to connect it to your account. Only the JIRA Global Admin credentials can be used here. After filling in all of the fields, press "Connect" at the bottom of the page to proceed:

image 1 (83).png

For help on inputting your token, you can check out the instructions to locate your credentials in the Jira Server & Data Center Integration article.


Import data

Step 1

After connecting your Jira account, you will see the following screen. Search for the project you wish to import and click "Next":


Step 2

Then select the type of issue you wish to import and click "Next":


Step 3

Then select which components to import and click "Next":


Step 4

In the final step, select the epics you wish to import and click "Done":


That's it! The data you selected will be imported into a new board.


Your import board

Your board will likely look something like this:



By default, your data will import the Jira Summary to the first column (also called the Name column). All other fields from Jira will be entered into the column with the matching name. For example, your Story Points in Jira will be populated in the "Story points" column on your board.


Note: This can not be changed prior to import. To change this after your initial import, see the instructions in Supported fields for mapping.


Components will pull in as their own individual items even though they are categories containing issues. The import also doesn't use subitems. The "Jira Issue" column is a link that will take you to the issue in Jira.


Pulling in the assignee

Contact permissions

If you want to pull a person into the "Assignee" column on, you need to change Contact permissions in Jira to "Anyone" for each individual. The following images are of Jira Cloud, but the requirements are the same for Jira Server + Data Center. To change the contact permissions, enter your Jira account, click on your avatar and choose "Account Settings". Then, select "Profile and visibility":


Scroll down to "Contact" and next to your email address, choose "Anyone":



Populating the "Assignee" column

To properly populate the "Assignee" column, the email address for the individual on must be the same as the email address for the individual in Jira Cloud or Jira Server.

If the email address is not public in Jira, then the Jira display name will be used instead of the email address to find a match on for the "Assignee". For this to work, the display name on needs to be the same as the display name in Jira.

If there are two users with the same display name on and in Jira, the "Assignee" column will populate with both people.


Sync future changes

When you import data from Jira, a Jira Integration recipe is created. To access the recipe, click on the "Integrate" icon at the top of your board:


Choose "Board Integrations" from the overhead menu. The integration recipe is as follows:


When an item is created in Jira and meets the criteria you selected when importing, an item will be created in All future changes made to the imported items will be reflected on your board.


Tip: If you wish to edit this connection or the criteria used to pull in information from Jira, use the three-dot menu at the upper right-hand corner of the recipe to select "Edit Integration" and make changes.



Supported fields for mapping 

While you can't change the way data is mapped from Jira to prior to your initial import, you can change the mapping after the initial import by editing the integration recipe mentioned in the last section of this article. If you wish to edit the mapping, use the three-dot menu at the upper right-hand corner of the recipe to select "Edit Integration". On the next screen, click on the word "item" to make changes.


Currently, the following fields are supported for mapping between Jira and

Show me the supported fields
issuekey, issuetype, project, string, priority, user, status, option, resolution, number, watches, datetime, date, progress, time spent, and votes
  • If using "time spent", the associated data will only sync to after the task is marked as done in JIRA.
  • If using "epic link (name)", please note that it is supported in all issue types excluding "epic" and "issue (any)". To get the "epic name" on "epic" issue types select "summary".
  • All Jira custom fields can be mapped into a status column in, as long as the custom field type is one that is supported (see above).
Note: At the moment, team-managed projects (formerly called "next-generation projects") are not supported. 



If you have any questions, please reach out to our team right here. We’re available 24/7 and happy to help.