6 min read

Feature

Note: The integration outlined in this article replaces the old Jira Cloud integration that we used to have. The old integration has since been deprecated, so please make sure to use the one described in this article instead!

We worked hard to create a new Jira Cloud integration for you, which now replaced the previous one that you may be familiar with! With this Jira Cloud integration, you will:

• No longer need a token or to be an admin to set up this integration.
  • If a user can edit an issue in Jira, then changes can also be made by the integration using that individual's credentials to set up the integration.
  • The integration will then continue to use the level of API permissions available to the user who set up the integration.
• Be able to utilize team-managed projects
• Have access to additional supported fields
• Enjoy our new and improved two-way sync option
• Experience a beautiful and simplified new design!

Add the integration

To add the integration to board, start by opening the Integrations Center and searching for "Jira". Make sure to select the integration that says "by monday.com" and not the one that says "Deprecated":

The integration has one recipe that contains the power of several smaller recipes! Click "Add to board" to begin customizing it.

After selecting your recipe for the first time, it's time to establish the connection between Jira and monday.com! Click on the Jira logo at the start of the recipe and choose "Connect". You'll be redirected to Atlassian to enter your credentials.

Note: You only need your credentials to get started. Unlike previous versions of this integration, you do not need to be an admin to set up the integration and you do not need to collect or submit a token.

When you set up a recipe for the first time and make the initial connection with your Jira account, you will be asked to review a list of permissions. Read this carefully to make sure you understand how the new integration works. If you agree to the parameters of the connection, click "Accept" to be redirected back to monday.com.

Note: The Jira integration will not work retroactively. Issues, epics, etc. that were created before the integration was set up will need to be updated in order for them to sync. Everything newly created and updated after setting up the integration will sync.

Customize your recipe

Once you've connected your account, you have a world of customization options ahead of you! For this example, we're looking at the following recipe: "Sync between Jira issues in this project of this type and items on this board with these fields"

We'll start by choosing the direction of the sync. You have the option of moving data into monday.com from Jira or into Jira from monday.com, or in both directions!

Then, by using the "this project" and "this type" fields, you can select the specific project and type of issues that will be synced to/from Jira.

Finally, when choosing "these fields" for your sync, you'll have the ability to select the Jira issue type, define the monday.com field, and also determine how future updates will be synced. You can change the sync direction of updated fields, regardless of the sync direction you choose earlier for creations.

Note: While the new Jira Cloud integration is great for syncing between editable fields, some default and uneditable fields (such as item ID, issue key, or link to issue) will not work as neither system allows for these to be changed once the item/issue has been created.

 

 

Create a two-way sync

A two-way sync occurs when data is being both pushed from monday.com into Jira and pulled from Jira into monday.com. This makes it so that your data matches within both platforms and remains up-to-date.

The nature of this recipe allows you to choose the direction of your sync in order to create a two-way sync between Jira and monday.com.

As mentioned in the previous section of this article, when you set up this recipe, you'll be asked to map future changes between Jira and monday.com when clicking on "these fields". You can change the sync direction of updated fields in this step, regardless of the sync direction you choose earlier when clicking on "Sync" at the beginning of the recipe.

Setting up the two-way sync

When you're mapping "these fields", you will select the field in Jira, the field in monday.com, and the direction that you want the sync to occur (two-ways).

For example, using the GIF below, if you want to map your item's "Name" on monday.com to the "Parent Name" in Jira, you will select those fields beneath the respective company's logo. Then, under the "Choose direction" dropdown you can choose "Both ways" to indicate that the information will travel in both directions.

 

Compatible Jira fields

The following fields are supported when mapping from Jira into monday.com:

From Jira > monday.com

• component
• issuekey
• issuetype
• project
• string
• priority
• user
• status
• radio button
• resolution
• number
• watches
• datetime
• date
• progress
• votes
• time spent
• person
• fix version
• sprint: including start date, end date, and goal
• story points
• epic: including epic assignee
• epic link
  • Note: 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".
• assignee
  • Note: Check out the "Pull in the assignee" section of this article for specific steps to follow.
• time spent
  • Note: If using "time spent", the associated data will only sync to monday.com after the task is marked as done in JIRA.
• custom entities
• 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). 

 

The following fields are supported for mapping from monday.com to Jira (the reverse of the above):

From monday.com > Jira

• string
• priority
• person
• radio button
• number
• datetime
• date
• assignee
  • Note: The monday.com people column isn't supported. A text or email column type can be used instead.
    
• status
  • Note: Because Jira allows you to build a workflow that transitions between different statuses, not every change in monday.com will change your Jira issue's status. The changes that would affect the status in Jira are the changes that apply to the workflow in Jira. If you change the status in monday.com to a label that Jira can't interpret, then you will receive a notification that the change didn't affect your issue in Jira.

Note: In the new Jira Cloud integration, team-managed projects (formerly called "next-generation projects") are supported! 🎉

 

Compatible monday.com columns

For an overview of the monday.com columns that are currently supported when mapping from monday.com into Jira, open the drop-down and take a look at the table.

Is your monday.com column supported? Take a look at the table.

Column	Supported?	Notes
People	Yes
Status	Yes
Formula	No
Timeline	No
Date	Yes	Date is supported, but time is not.
Time Tracking	No
Auto Number	No
Item ID	No
Phone	Yes
File	Yes
Link to Item	No
Mirror	No
DropDown	No
Location	No
Email	Yes
Tags	No
Text	Yes
Progress	No
Link	Yes	​
Numbers	Yes
Last Updated	No
World Clock	No
Country	No
Long Text	Yes
Checkbox	Yes
Vote	No
Rating	Yes
Creation Log	No
Week	No
Updates	Yes*	Not a real time sync. It will only sync the original data.
Color Picker	No

 

Tip: While there is no integration column available for this yet, you can use the Code and URL to instantly access your Jira issue!

 

How to import data from Jira

While there is no direct way to import data from Jira into monday.com, starting a recipe will trigger an import. Watch the video below to understand more about how this works:  

 

How to delete a recipe

You can turn off and/or delete your integration recipe in the integration menu- 

You can also edit the integration and the Jira account you want to connect to.

Troubleshoot the integration

Are you experiencing any issues with the Jira Cloud integration? Check out some of the common issues and solutions below to help get your Jira Cloud integration back on track and working properly. ⬇️

• Issue:
  

I've connected Jira to my monday.com board and mapped out my users, but they aren't coming across to the monday.com board.

• Solution:
  

You may have the "Default profile visibility" settings in Jira set up to hide your email address from external applications such as monday.com. This means that monday.com cannot access the user's email address to map them accordingly with your monday.com board. In order to fix this, you will have to allow "unhide the email address" in your visibility settings in Jira. Learn more here.

• Issue:

I'm an admin and connected Jira to my monday.com board and mapped out my users. However, triggering an automation related to me works, but it doesn't work when I trigger an automation with another user.

• Solution:
  

Your default profile visibility settings in Jira could be set up to hide your email address from external applications such as monday.com. monday.com has access to your users email as you're the one who has made the connection and can share your email. However, you cannot share user's email addresses in Jira to monday.com when they are hidden. In order to fix this, you will have to allow "unhide the email address" in your visibility settings in Jira. Learn more here.

• Issue: 

A project can be selected, but the issue type is blank.

• Solution:
  

In this case, the user who is setting up the integration does not have the correct Jira project permissions. The Jira project permissions are blocking the selection of the Jira issue type field. As a result, the issue type field displays as blank. To resolve this, change the permissions in your Jira account.