By Alpit Patel and the aibrevo team · October 20, 2026 · 5 min read
monday.com Jira Integration: Setup, Two-Way Sync, Field Limits and Plan Costs
Quick answer
Yes, monday.com integrates with Jira Cloud natively. The integration syncs Jira issues and monday items one way or both ways, with per-field direction, and needs the Standard plan or higher. Each sync uses integration actions: 250 a month on Standard, 25,000 on Pro. A newer Jira Two-way sync app (beta) polls every 3 minutes but cannot take over existing syncs.
Part of the guide: monday CRM guide
Key takeaways
- monday.com has a native Jira Cloud integration built by monday.com. You add it from the Integrations Center, connect with OAuth (no admin rights or API token needed), and choose one direction or both.
- Two-way sync is set per field. Many Jira fields map into monday, but fewer monday columns map back: Formula, Timeline, Mirror, Tags, Time Tracking and Link to Item columns are not supported.
- Nothing syncs retroactively. Issues and items created before setup only sync after someone updates them.
- Integrations need the Standard plan or higher. monday gives 250 integration actions a month on Standard, 25,000 on Pro and 250,000 on Enterprise, and each synced change uses actions. When the month's actions run out, editing or adding integrations is blocked.
- A newer Jira Cloud Two-way sync app is in beta. It polls every 3 minutes and supports Jira sub-tasks, but syncs built with the older integration cannot be moved into it.
Yes, monday.com integrates with Jira. The native Jira Cloud integration, built by monday.com, syncs Jira issues and monday items in one direction or both, with the direction set field by field. It is available on the Standard plan and above, and every sync uses integration actions from a monthly allowance: 250 on Standard, 25,000 on Pro. We read monday’s Jira Cloud integration, Jira Cloud Two-way sync app and plan articles on October 20, 2026.
The typical reason teams connect the two: sales or customer success works in monday.com, engineering works in Jira, and a customer request or bug needs to reach the developers without someone copying it by hand.
How do you set up the monday.com Jira integration?
- Open the board, open the Integrations Center and search for “Jira”.
- Pick the Jira integration labelled by monday.com, not the one marked “Deprecated”.
- Click Add to board on the sync recipe: “Sync between Jira issues in this project of this type and items on this board with these fields”.
- Click the Jira logo in the recipe and choose Connect. You sign in at Atlassian with OAuth, so monday never sees your Jira password. You do not need to be a Jira admin or create an API token.
- Choose the sync direction: Jira to monday, monday to Jira, or both.
- Pick the Jira project and issue type, then optional conditions (for example, skip issues with Low priority). Custom fields cannot be used as conditions.
- Click these fields and map each Jira field to a monday column, with a direction for updates. Choose both ways for a two-way field.
- Click Add to board.
Which fields sync between Jira and monday.com?
The mapping is lopsided: most Jira fields can come into monday, but fewer monday columns can go back to Jira.
| monday.com column | Syncs to Jira? |
|---|---|
| People, Status, Phone, File, Dropdown, Email, Text, Link | Yes |
| Date | Yes, date only (no time) |
| Formula, Timeline, Time Tracking, Auto Number, Item ID, Link to Item, Mirror, Location, Tags, Progress | No |
From Jira into monday, the article lists fields including status, priority, assignee, labels, components, fix version, sprint (with start date, end date and goal), story points, epic and epic link, time spent and custom fields of supported types. Two details catch people out:
- Status changes follow your Jira workflow. If you set a monday status that is not a valid transition in Jira, the Jira issue does not change and you get a notification.
- Time spent only reaches monday after the Jira task is marked done.
- Labels: a two-way mapping handles up to 1,000 labels.
What are the limits of the monday.com Jira integration?
| Limit | Original Jira Cloud integration | Jira Cloud Two-way sync app (beta) |
|---|---|---|
| Old issues and items | Not synced until updated | Not synced; only new items link |
| Who can edit the recipe | Only the user who connected Jira | Only the integration owner by default |
| Comments | Not stated | Not synced |
| Deletions | Not stated | Not synced, on purpose |
| Sub-tasks | Not stated | Jira sub-tasks to monday items (not subitems) |
| Sync timing | Not stated | Polls every 3 minutes, batches repeat updates |
| Moving between the two | Migration to the new app is not supported | Start from scratch or pause the old one first |
The owner rule matters more than it looks. The sync acts with the connecting person’s Jira permissions, and monday says the connection breaks if that person’s account is removed. Connect with a shared integration account if your team allows it, so a staff change does not stop the sync.
How many integration actions does a Jira sync use?
Every change the integration pushes or pulls uses actions, and monday counts integrations against a separate monthly pool from automations. monday’s automations and integrations pricing article lists:
Free and Basic plans do not include integrations at all, according to the same article.
Here is the arithmetic for a modest two-way sync. Say 15 Jira issues change each working day, and each change updates two mapped fields in monday. That is about 30 actions a day, or roughly 660 in a 22-day month, before any monday-to-Jira traffic. Standard’s 250 runs out in about a week (illustrative example; actual counts depend on your mapping).
monday's [actions article](https://support.monday.com/hc/en-us/articles/360017556179) says that when the month's actions are used up, the account cannot edit or add integrations, and only Enterprise accounts can buy more. monday itself recommends Enterprise for teams running several two-way syncs.Our monday CRM plan limits page tables the other per-plan caps.
Should you use the integration, the beta two-way app, or a third-party connector?
- Use the original Jira Cloud integration if you already run it and it works. Moving to the beta app means rebuilding and losing the link on already-synced items.
- Try the Jira Cloud Two-way sync app on a new board if you need filters on both sides, sub-task sync or clearer error logs in Run History. Expect beta changes.
- Use Jira Data Center integration if your Jira is self-hosted; monday lists it separately.
- Consider a marketplace connector or Zapier/Make if you need comment sync or field types monday does not map. Check the vendor’s own docs for what it supports.
If you are deciding whether monday.com should sit next to Jira at all, our monday.com CRM guide and monday CRM vs work management explain which product does what. Our monday.com implementation team builds and tests these syncs, including the action budget.
Sources
- monday.com support, The Jira Cloud integration, read October 20, 2026.
- monday.com support, Jira Cloud Two-way sync app (beta), read October 20, 2026.
- monday.com support, Automations and integrations pricing and Automation and Integration actions and limits, read October 20, 2026.