The Jira Cloud Two-way sync app allows you to create a bi-directional sync between monday.com and your Jira Cloud account. Keep your work aligned across both platforms without manual updates or copy-pasting between tools.

Migrating from an existing Jira Cloud integration

Migrating from an existing Jira Cloud integration to the Jira two-way sync app is not supported. 

Please keep the following in mind:

• New board: The simplest path is to set up the Jira Cloud Two-way sync app on a brand new board from scratch.
• Same board: If you want to use the same board as your existing integration, it's recommended to pause the old integration first, then activate the new two-way sync app. Use the two-way sync filters to define exactly which items to pull in and avoid creating duplicates.
• Previously synced items: Any items synced through the previous integration will stop syncing. They cannot be reconnected to the new setup at this time; only newly pulled items will sync going forward.

In all cases, you will need to remove the old integration manually and configure the Jira Cloud Two-way sync app from scratch. Keep reading to learn about the Jira Cloud two-way sync setup. 

How to use the Jira Cloud Two-way sync app

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

Click on the Jira 2-way-sync app to open the integration setup.

Set up the connection to Jira

To connect monday.com to Jira, click on the dropdown, choose a Jira account to connect, and log in with your Jira credentials. Unlike Jira Data Center, no admin-level on-premise profile setup is required. Any user with the appropriate Jira permissions can authenticate directly via OAuth 2.0.

Once authenticated, your connected Jira account will appear in the dropdown menu.

Setting up the integration

Sync Scope

Once connected, you will be prompted to set up the sync direction between your monday board and your Jira account.

Select your Jira site from the first dropdown, then choose your Jira project, and finally select the issue type you want to sync.

The data shown is based on your access and permissions in Jira. Fields or projects you do not have access to will not appear as options.

Field mapping

On the Map fields page, map which monday columns correspond to Jira fields. You can only map fields of the same type. The fields shown are those available based on your permissions and the selected issue layout.

If you choose two-way sync, you can decide the direction each field syncs. If you choose one-way, the order you select determines the direction the data flows.

Incoming data

On the Incoming data screen, set the conditions that determine when data is created or updated in monday.com. Items are created or updated only when these conditions are met.

To sync all records from Jira, leave the option set to any record. 

To filter which records come in, select a record that meets conditions and define your conditions.

Outgoing data

On the Outgoing data screen, set the conditions that determine when data is created or updated in Jira.
To sync all monday items to Jira, leave the option set to any item. 

To filter which items go to Jira, select When an item that meets conditions and add your conditions.
Once you have finished adding conditions, click Activate sync to complete the setup.

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

Configure a sync where a Jira Sub-task creates a monday item and keeps it bi-directionally synchronized. 

For example: 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

Configure a sync where a monday item creates a Jira Sub-task in a selected project with mapped fields, and future changes stay synchronized.

Permission scopes

The following are the permission scopes for the Jira integration:

READ

• Allows monday.com to view projects and issues that the user can view, including related items such as dashboards, filters, attachments, and comments. It also allows monday.com to view your user profile.

WRITE

• Allows monday.com to create, update, and delete projects and issues that the user can change, including related items such as dashboards, filters, attachments, and comments.

Permissions and ownership

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

If the integration owner's account is removed, the connection breaks because it relies on that person's credentials. Integrations can be transferred to another owner, but 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 surface directly in Run History with detailed explanations, including messages from 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.com with Jira 

The connection between monday.com and Jira is established using OAuth 2.0, the industry standard for authentication and authorization. This ensures data access and actions are always performed within the boundaries of each user's Jira permissions.

Individual users authenticate directly with Jira via OAuth. monday.com never receives your Jira password. Every action, from viewing items to updating issues, is carried out based on your own Jira permissions. No shared credentials or admin access are required.

Known limitations

• It is not possible to retroactively map existing items. To generate links between both platforms, the integration must be triggered and new items need to be created in monday.com or new issues in Jira.
•  
• Sub-task scope supports a single Sub-task type per app configuration.
• Jira Sub-tasks sync with monday items only. Mapping Jira Sub-tasks to monday subitems is not supported.
• Syncing Jira comments to monday is not supported.
• Deletions of a Jira issue or a monday item are intentionally not supported to avoid data loss.

FAQ

Do I need an admin to set up the Jira connection?

No. Unlike Jira Data Center, Jira does not require an admin to create an on-premise profile first. Any user with the appropriate Jira permissions can authenticate directly.

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.

How often does data sync between monday.com and Jira ?

Data syncs every 3 minutes. Multiple updates to the same record within a 3-minute window are batched into a single API call.

Where can I troubleshoot a Jira sync issue?

Open Run History to review detailed error messages, including messages from Jira. You can also use the Autopilot Hub to monitor all integrations and get suggested root causes.