6 min read

Feature

We worked hard to create a new Jira Cloud integration for you. It has 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!

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!

Add the integration

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

Note: Multiple instances of Jira are supported in the monday integration, however we do not recommend connecting them in the same board. 

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

After selecting the recipe, 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. We use OAuth to make the connection, so monday.com will never have access to your Jira login 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 a token.

When you 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 terms, 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 will need to be updated in order for them to sync. Everything created or updated after setting up the integration will sync.

Customize your recipe

Choose the direction of your sync

Once you've connected your account, you have a world of customization options available to you! For this example, consider the following recipe:

"Sync between Jira issues in this project of this type and items on this board with these fields"

After connecting your Jira account with the Jira icon, start by choosing the direction of the sync. You have the option of moving data:

• into monday.com from Jira
• into Jira from monday.com
• or in both directions!

Choose the Jira project to connect to

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.

Set conditions for the sync

Then, you can select the conditions for the issues that you want to sync. While custom fields can't be used to set conditions, you have a ton of options! In this example, we're choosing to sync all issues where the "Priority" is not "Low" or "Lowest":

You can then define the conditions that must be met in order for items on your monday board to sync with Jira. If you know exactly what you're looking for, you can type to quickly locate it within the dropdown.

Note: Because Jira syncs with a specific user rather than an entire account, only the individual who connected their Jira account with monday.com can edit the recipe(s) added to a board. This is true regardless of who the board owners are.

Decide how to manage updates

Click on "these fields" to open your final customization options. Regardless of the direction you chose for syncing newly created items and issues, you can choose to change the sync direction for any updates to existing items or issues.

Here you can select a Jira issue field, a monday.com item field, and the direction that you would like to sync future updates-- whether you would like updates to Jira issues to update items in monday.com, the other way around, or both! 

Note: Some default fields are not able to be edited. Some examples are: item ID, issue key, link to issue, etc. Because these fields can not be edited after an issue is created, they will not sync.

 

That's it! Once you're done customizing, click "Add To Board" to watch the integration work!

 

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". Regardless of the direction you chose for syncing newly created items and issues when clicking "Sync" during set up, you can choose to change the sync direction for any updates to existing items or issues when clicking "these fields".

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. To create a two-way sync, select "both ways".

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

 

Note: You can push or pull up to 1,000 labels when mapping a two-way sync between monday.com and Jira.

 

Compatible Jira fields

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

From Jira > monday.com

• boolean
• component - name and description
• date
• datetime
• fix version - name and description
• group
• issuekey
• issuetype
• labels
• number
• priority
• progress
• project
• radio button
• resolution
• status
• string
• user
• votes
• watches
• time spent
• person
• 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 opposite of the above):

From monday.com > Jira

• date
• datetime
• dropdown
• email
• link
• priority
• person
• radio button
• string
• number
• 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	Yes
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*	Information will only be retrieved once. The recipe will pull data only from the first update that is being created, and not from updates thereafter.
Color Picker	No

 

Tip: You can use the URL in the "Link" column to instantly access your issue in Jira!

 

 

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:

 

Note: There is a limitation on Jira's side that only 100-150 issues in Jira can be updated and synced with monday every 5 minutes.

 

 

How to delete a recipe

To delete or pause your recipe, visit the active "Board Integrations" tab in the Integrations Center. To pause or resume your integration, toggle the switch off or on. To delete the integration, open the integration menu using the three-dot icon and select "Delete Integration":

In the integration menu, you can also view the integration's activity, edit the recipe, or duplicate the recipe.

 

 

Troubleshooting

These are some common issues and solutions: 

 

Issue #1

I connected Jira to my monday.com board and mapped out my users. Even so, my users 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 select "unhide the email address" in your visibility settings in Jira. Learn more here.

 

Issue #2

I'm an admin. I connected Jira to my monday.com board and mapped out my users. Triggering an automation works for me, but it doesn't work when I trigger an automation for 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. In this case, monday.com has access to the email connected to your user profile because you're the one who made the connection. So permission was granted to share your email. However, you cannot share another user's email address with Jira via monday.com when they are hidden. In order to fix this, you will have to select "unhide the email address" in your visibility settings in Jira. Learn more here.

 

Issue #3

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.