In order to log in and authenticate to Jira Data Center for the first time, you (the Jira admin) will need to complete two steps:

1. Create a new Jira instance - you as the admin need to connect the general account

2. Connect to a Jira user - only after a new instance is created, then each user can connect their user profile to that same general account

If the Jira admin has already connected the instance, individual users can connect their user profiles.

Creating a new Jira Instance 

To create a new Jira instance, click on Administration and then navigate to Application links on the left side panel. Click on Create link:

Next, select External application under Application type, and Incoming under Direction:

Next, you'll see a page called Configure an incoming link. Fill out the form like this:

Name: Enter a unique name for the link
Redirect URL: https://integrations-by-monday-jiradc.monday.com/oauth/callback/app/jira-data-center

(copy and paste the above URL exactly as is)

Permission: System admin

Lastly, click on Save. You're now done setting up a new Jira instance.

Connecting to your Jira Data Center Account 

To connect your Jira Data Center Account to the template on monday.com, first choose the template you wish to use. To connect to your Jira account, you will need to click on the Jira icon and then click on Connect as seen below:

Next, you'll seen this screen, which will ask you to connect to whichever Jira Data Center account you need:

You can also add a new Jira Data Center by clicking on + Add new Jira Data Center in the dropdown menu.

To find your Client ID and Client secret:

Log into your Jira account, click on the settings icon in the top right corner and then click on Applications. Navigate to Integrations on the left side panel, and then click on Application links.

Click on the three dots next to the application (please note: an application needs to be created on Jira before being able to use it, please refer to Jira documentation for guidance) you're using, then on view credentials, where you will see the option to copy your client ID and client secret:

To find the Base URL, navigate to Jira, and then click on Administration tab in the settings icon on the top right corner of the navbar. Next, click on System and then copy the value listed next to Base URL.

Once you have all your credentials, fill them out as shown below:

When done, click on Connect. You will then be redirected to a Jira screen that will ask you to grant monday access to your Jira account. Click on Allow.

The initial setup is now finished! 🎉 Now everyone in your account can set up their individual users.

Using a Jira Data Center template

In order to use a template, once the initial connection is established, you then need to click on the Jira icon and then choose which Jira Data Center connection you want to use.

Then you can fill out the rest of the template as you need.

Creating 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 in both platforms and remains up-to-date.

To create a two-way sync for new creations, click on Sync and choose which direction you want to use for new creations.

To choose a sync direction between fields, click on these fields in order to map the integration between Jira and monday.

Supported fields for mapping

The following fields are supported for mapping the integration from Jira to monday.com:

From Jira to 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
  • 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
  • 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

The following fields are supported for mapping the integration from monday.com to Jira:

From monday.com to Jira

• date
• datetime
• dropdown
• email
• link 
• priority
• person
• radio button
• string
• number
• assignee

  • The monday.com people column isn't supported. A text or email column type can be used instead

• status

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

Once you have filled out all of the options in the template, it is ready to be used.

How to delete the integration

To delete the integration, navigate to the Automation center and then select the Board Automations tab. Click on the three dot menu on the right side of the Jira Data Center integration and click on Delete Integration.

Important to know

• The user creating the integration must make sure to map the item name to the summary field. If not, the integration will fail when it attempts to run
• The Jira Data Center app does not offer the option to select "Any" as an option for the issue/project. You must select the specific issue/project in order to sync it
• Team-managed projects (formerly called "next-generation projects") are supported in the integration

 Permission scopes

Why are we asking for permission to access your information?

Permission scopes are a way to define and control what an application can access or do on behalf of a user when integrating with another service. They specify the types of data and actions the integration is allowed to access or perform.

When you connect two services, one service might need access to certain information from the other to function properly. Permission scopes ensure that the integration only has access to the specific data it needs to perform its tasks, such as reading calendar events or creating tasks, without accessing unrelated data. This helps protect your privacy by limiting the integration's access to only what is necessary for its intended functionality.

Specific to the Jira Data Center Integration

The following are the permission scopes for the Jira Data Center Integration:

• READ
  • This allows monday.com to view projects and issues that the user can view, including any related items, such as dashboards, filters, attachments, or comments. It also allows monday.com to view your user profile.
• WRITE
  • This allows monday.com to create, update, and delete projects and issues that the user can change, including any related items, such as dashboards, filters, attachments, or comments.
• ADMIN
  • This is required so that monday.com can create webhooks from within Jira Data Center. This allows Jira to notify monday.com about created and changed items and is instrumental in allowing the sync to work between the two platforms.

Learn more about what these different scopes mean on Atlassian's website.

We want to hear from you

As we continue to improve this feature, we would love to hear your feedback. If you have any comments, suggestions, or questions, please fill out this form.