What can we help you with?

The new Jira Cloud integration

 

Screen_Shot_2020-03-15_at_15.57.05.png

 

We're excited to introduce a new and improved Jira Cloud integration! Our new integration has a few key differences from the previous integration. This article will cover how you can manage your tasks, issues, and bugs in Jira Cloud and monday.com!

Note: This integration works only for the person who initially created it, and for those who have their Jira email visibility settings set to "Anyone" as shown below.

jira_email_settings.png

 

About the new Jira Cloud integration

The new Jira Cloud integration, as detailed in this article, is currently in beta. We're working hard to build something great for you! For now, the new integration will not replace the previous integration. You'll have the ability to access one version or the other while we work to make the new integration encompass all of the benefits of both versions.

A few notable changes:

  • You 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.
  • Team-managed projects are now supported.
  • Additional supported fields.
  • A beautiful and simplified new design!

 

Add the integration

Step 1: Open the Integrations Center

To add the Jira Cloud integration, you'll start by opening the Integrations Center.

To open the Integrations Center, go to the board where you'd like to use the integration and click on the "Integrate" icon in the top right corner.

Frame_80.png

 

Step 2: Search for "Jira"

All integrations are organized into categories on the left side which can help you filter out relevant integrations for your industry. To find the integration, we recommend searching for "Jira". Choose the integration with the "Beta" banner.

Frame_81.png

 

Step 3: Select the recipe

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

Frame_82.png

 

Step 4: Establish your account connection

Once you select the recipe, you can customize it. First, you will click on the Jira logo at the start of the recipe and choose "Connect". You'll be redirected to Atlassian to enter your credentials.

Frame_83.png

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.

 

Step 5: Review and "Accept"

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.

Frame_84.png

 

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.

Frame_75.png

When you click on any other customizable field, you will be asked to get specific. Choose the project and the type. When customizing your integration and choosing the "fields" for your sync, you'll also have the ability to 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.

Frame_85.png

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.

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 the beta recipe allows you to choose the direction of your sync.

Frame_78.png

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.

 

Choosing the direction for your sync

When you're mapping, you will select the field in Jira, the field in monday.com, and the direction that you want the sync to occur. For example, using the image 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, you will choose the arrow between them to indicate the direction the information will travel.

Frame_86.png
The tip of the arrow will point towards the platform that will receive the data and away from the platform sending the data. For now, changes can only flow in one direction. Our team is working hard to make this sync work both ways.

 

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

 

How to delete a recipe

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

Frame_68.png

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, when I trigger an automation relating to me it works, but when I trigger an automation with another user it doesn't work.

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

 

 

If you have any questions, please reach out to our team using our contact form. We're available 24/7 and happy to help!

Have more questions? Submit a request