With a couple of clicks, you can easily import your work from Jira into monday.com!
Connect your account
Go to your profile picture in the bottom left corner of the screen and click on "Import data":
Click on Jira or Jira Server + Data Center:
Alternatively, you can also begin this import by clicking on "Add" at the top of the left pane > "Import data" > "jira" or "jira server":
You will then see a page prompting you to enter your Jira information and connect it to your monday.com account. Only the JIRA Global Admin credentials can be used here. In the image below, we're integrating with Jira Cloud.
To input your Jira Cloud token, go to Jira and click your profile avatar in the top right corner of the screen. Select "Account Settings", then "Security", then scroll down to click "Create and manage API tokens". From there, create an API token and copy the token to input on the connection screen above.
But if you're hoping to integrate with Jira Server, check out the instructions to locate your credentials in the Jira Server & Data Center Integration article.
After filling in all fields, press "Connect" at the bottom of the page to proceed:
After connecting your Jira account, you will see the following screen. Search for the project you wish to import and click "Next":
Then select the type of issue you wish to import and click "Next":
Then select which components to import and click "Next":
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 monday.com board will likely look something like this:
How the board is structured
By default, your data will import the Jira Summary to the first monday.com column (also called the Name column). All other fields from Jira will be entered into the monday.com column with the matching name. For example, your Story Points in Jira will be populated in the "Story points" column on your board.
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.
If you want to pull a person into the "Assignee" column on monday.com, 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 monday.com 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 monday.com for the "Assignee". For this to work, the display name on monday.com needs to be the same as the display name in Jira.
If there are two users with the same display name on monday.com 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 monday.com. All future changes made to the imported items will be reflected on your monday.com board.
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.
While you can't change the way data is mapped from Jira to monday.com 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 monday.com: 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 monday.com 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 monday.com, as long as the custom field type is one that is supported (see above).
If you need help building custom integrations, we also have an option for paid assistance through our network of certified monday.com partners. If you're interested, please fill out this form and someone will be in touch shortly!
If you have any questions, please reach out to our team by using our contact form. We're available 24/7 and happy to help!