The Jira Two-way sync app is the solution for you to create a bi-directional sync between monday and your Jira account, all in one place so you can easily manage and track this connection.

Creating a new Jira Instance

If you do not already have a Jira instance created, you will need to create one. If you do, skip this section.

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://apps-credentials.monday.com/authorize/oauth2/redirect-uri

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

How to use the Jira Two-way sync app

Click on the Integrate button at the top of the screen for the board you want to use the app for, and then search for Jira Data Center.

Click on the Jira Data Center app:

Set up the connection to Jira Data Center

Connecting to Jira is a two-step process: an initial handshake completed by the Jira admin, followed by a user-driven connection step using OAuth 2.0.

Admins only

Only account admins can create a shareable Jira connection for their organization. To set it up, open the Administration section, then select the Connection tab and click On-premise profiles.

Click on the + New profile button, and then enter the Base URL, Client ID and Client secret from your Jira Data Center instance and then save your changes.

You can share this with everyone on your account or limit it to specific teams and people. The profile you created will now be available to the users you shared it with when they connect. 

Non-admin users

To connect monday to Jira DC for the first time you will need the admin to share the on prem profile of your jira instance with you. If he did the profile will show up under the drop down. This will enable your initial handshake with the Jira instance.

The Base URL may be populated automatically (if not, you will need to add it in manually). The Base URL is the one being used at your organization.

Once you've done that, click on the Continue to Jira Data Center button:

A pop-up will appear asking you to connect to your Jira Data Center instance and grant permission to view projects and create issues in Jira. After you log in and approve the permissions, you will be redirected back to monday, and the connected Jira account will appear in the dropdown menu.

Setting up the integration

Sync Scope

Once an on-premise profile has been made, you will be prompted to set up the sync direction between the monday board and your Jira account.

Choose the Jira project from the dropdown menu. The data that you see on this page is based on the access and permissions that you have in Jira. If you don't have access to a certain field, it will not appear as an option in the dropdown menu.

Next, you need to choose which Jira issue types will be used on this board:

Once the sync has been set up, click Next to continue.

Field mapping 

On the Map fields page, you can map out which columns in monday will match the Jira fields. You can choose compatible Jira fields from the dropdown menus.

You can only map fields of the same type. The fields you see are the ones to which you have access (according to your relevant permissions) and appear on the epic layout.

If you choose two-way sync, you can decide which way the data will be mapped for each field. If you choose one way, the order you select will determine the direction in which the data is synced.

Incoming data

Once you reach the Incoming data screen, you can determine the conditions that will define when data is created or updated on the monday platform.

The items with the mapped fields will be created or updated only if these conditions are met.

If you want all records from Jira to be synced to monday, you can leave the option as any record.

If you want to choose which specific records come in from Jira, you can select the a record that meets conditions option and then add your conditions. You can create a condition and/or grouping.

Outgoing data 

On the Outgoing data screen,  you can determine the conditions that will define when data is created or updated on the Jira platform.

The items with the mapped fields will be created or updated only if these conditions are met.

If you want all items from monday to be synced to Jira, you can leave the option set to any item.

If you want to choose which specific items go into Jira, you can choose the When an item that meets conditions and add your conditions.

Once you have finished adding conditions or don't have any to add, click Activate sync to set up the integration.

Syncing Jira Sub-tasks with monday items

You can configure the Jira Two-way sync app to support sub-level and cross-level mappings between Jira Sub-tasks and monday items.

Jira Sub-task → monday item

An integration builder can configure a sync where a Jira Sub-task creates a monday item and keeps it bi-directionally synchronized.

Use case: When a Sub-task is created or updated in a selected Jira project, create a monday item and sync future changes.

monday item → Jira Sub-task

An integration builder can configure a sync where a monday item creates a Jira Sub-task in a selected project with mapped fields, and sync future changes.

What the integration looks like on the board Automations page

Once completed, the integration will appear in the Board Automations page in a summarized form. The arrows in the middle of the integration template will change to reflect the integration's configuration.

Permission scopes 

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

READ

WRITE

Permissions and ownership

Updates are performed on behalf of the connected integration/system user. If you use a dedicated integration account, all sync changes will appear with that account appearing as the "user".

If the integration owner’s account is removed, the connection breaks because it uses that person’s connections. Integrations can be transferred to another owner, but integrations must be re-authenticated by a new user with the correct permissions.

Editing: By default, only the integration owner can edit configurations. Viewing access for non-owners is limited for security reasons. However, all users can see synced data on boards, and errors appear in Run History.

Run history is stored for a limited period (a few weeks). If an integration or board is deleted, its run history will eventually disappear after this retention period.

The polling mechanism

We use a polling mechanism to sync data every 3 minutes. In the event that multiple changes occur during the 3-minute polling window, the new integration uses caching, so that multiple updates to the same record within a short time will only trigger one API call, greatly reducing load and performance.

Errors and troubleshooting

Errors now surface directly in Run History with detailed explanations, including messages from the third-party system (Salesforce or Jira). This gives full visibility into what went wrong and where.

During setup, an AI-assisted field auto-mapping tool is there to help. In addition, the Autopilot Hub monitors all automations and integrations in one place, using AI to suggest likely root causes of issues.

If some fields update successfully but others fail, then the entire run is marked as failed. This prevents overlooking partial errors. You can then correct the issue and re-run.

Connecting monday with Jira Data Center

The connection between monday and Jira Data Center is established securely using OAuth 2.0 - the industry standard for authentication and authorization. This setup ensures that data access and actions are always performed within the boundaries of each user’s Jira permissions.

One-Time Admin Setup

To start, a Jira admin needs to create an OAuth app in Jira Data Center. This generates a Client ID and Client Secret, which are used once during the initial setup in monday. These client credentials (Client ID & Client Secret) establish a trusted connection between monday and your Jira Data Center. They’re used only during OAuth token exchanges.

Individual User Connections

Once the initial trust is established, Individual users then authenticate directly with Jira (via OAuth/SSO); monday never receives their passwords. This means every action - from viewing items to updating issues, is carried out based on the user’s own Jira permissions. No shared credentials or admin access are required, keeping the integration both flexible and secure.

Migration to Jira Data Center 2-way sync

monday.com is introducing a new 2-way sync integration app for the Jira Data Center integration. The 2-way sync option is available directly on monday without the need for a third party tool or limiting one-way automations, making it much easier to use than other tools.

This new app replaces the legacy one-way integration templates with a more scalable, secure, and flexible solution that keeps data aligned across platforms in real time.

Known limitations

Please check out the benefits article to learn more.

FAQ

Can I sync Jira Sub-tasks to monday subitems?

Jira Sub-tasks sync with monday items only. Mapping Jira Sub-tasks to monday subitems is not supported.

Can the Jira Two-way sync app create a monday item from a Jira Sub-task?

Yes. You can configure a two-way sync where Jira Sub-tasks create monday items and changes stay synchronized in both directions.

Can a monday item create a Jira Sub-task and sync updates?

Yes. You can configure a two-way sync where a monday item creates a Jira Sub-task in a selected project and future changes stay synchronized.

Do I need to pick a specific Jira Sub-task type to sync?

Yes. Sub-task scope supports a single Sub-task type per app configuration.

Do parent-level Jira issue mappings still work if I also sync Sub-tasks?

Yes. Parent-level mappings remain supported.