monday.com and Jira, ready to switch on
An item moved into the group you name becomes a Jira issue with your columns mapped, every Jira status is paired with one of your status labels, sprint dates fill the timeline column, and updates travel as comments with their author. You paste two keys in your account and it runs, in about ten minutes.
No setup fee, cancel any month, and a person on live chat if a key doesn't work.
More with these apps: all monday.com integrations · all Jira integrations
monday.com already has a Jira integration.
It has: monday.com's page describes turning incoming items into Jira issues and keeping both teams up to date, and its support notes that several Jira instances can be used on one board. If you're on a plan with integrations and it fits, use it. This pair is one fixed rule at a flat price, written by a person and watched.
What moves, and when
The details you would normally get after a sales call. Here they are up front.
| What | Direction | When | Rule |
|---|---|---|---|
| Item enters the group | monday.com to Jira | When it moves into the group you name | Becomes an issue with your columns mapped: text to summary, long text to description, date to due date |
| Status label per Jira status | Jira to monday.com | Within seconds | Each Jira status is paired with one of your labels, in your own colours and words |
| Timeline from the sprint | Jira to monday.com | When the sprint is set | The timeline column follows the sprint dates, so a Gantt on the board is honest |
| Updates as comments | Both ways | Within seconds | A monday.com update becomes a Jira comment with the author, and a Jira comment posts as an update |
| People column to assignee | Both ways | With every change | Matched by email, with a fallback so nothing lands unassigned |
| Ids on both sides | Both ways | Every change | The issue key in a column, the item id on the issue, so a retried change never opens a second issue |
How to set up monday.com and Jira
Ten minutes of your time, then it's ours.
- Choose monday.com and JiraPress Connect. This pair is already selected on the checkout page at $39 a month, and there's nothing else to pick.
- Pay and open your accountCard or invoice, about two minutes. The account opens with this integration waiting for its two keys.
- Paste the monday.com API token and the Jira Cloud API token
- monday.com API token: in monday.com press your profile picture in the top right and select Developers. The Developer Center opens in a new tab. Full monday.com guide
- Jira Cloud API token: open id.atlassian.com/manage-profile/security/api-tokens and press Create API token. Full Jira guide
Each screen carries the full guide with the exact menu names, about five minutes for both. - We check both keysEach key is checked against monday.com's and Jira's own API the moment you paste it. If one doesn't pass, the screen says what to fix, and a person joins the chat if that isn't enough.
- Create one test item, then it's RunningA minute or two. Create a item in monday.com, watch its twin appear in Jira, then close one and watch the other close.
When monday.com or Jira changes its API, we fix it within a working day. You don't get a ticket to solve.
- Everything in the table above, with monitoring on.
- Fixes when either app changes its API.
- A person on live chat, replies within a working hour.
- Custom logic beyond the table is priced separately.
No setup fee, cancel any month
Ways to connect monday.com and Jira
Three ways people connect these two, and what each one asks of you. The built-in app is described above.
Before you decide
Which one is the source of truth?
Neither, and that is why the loop guard matters. Each team works where it prefers, and the twin follows. If you would rather one side be read-only, say so and we set it that way.
Do subtasks and checklists come across?
The top level does, with title, dates and assignee. Subtasks and checklists differ so much between these two that we treat them as a custom job rather than pretending they map cleanly.
Does it spend our monday.com automation actions?
No. It runs outside your account through the API, so it counts against neither the automation nor the integration actions your plan includes. That's often the reason people ask for it.
Which group starts an issue?
The one you name, usually Ready for dev. Everything in other groups stays on the board.
What can monday.com integrate with?
Ready-made on Dovetly, monday.com pairs with Trello, Slack, ClickUp, Pipedrive, Stripe, ActiveCampaign and Jira. All of them use one API token from the Developer Center and address columns by id, so renaming a column later breaks nothing. Anything else, describe it and a person replies with a price within a working hour.
How do I set up the Jira integration?
Paste two keys: a monday.com API token from the Developer Center and a Jira Cloud API token from id.atlassian.com. Name the group that should start issues, usually Ready for dev, and pair each Jira status with one of your labels. An item moved into that group becomes an issue with your columns mapped, and sprint dates fill the timeline column.
Is the Jira API free?
You don't buy anything extra from Atlassian for this pair. The API token is created in your Atlassian account at id.atlassian.com on the Jira Cloud plan you already have. Our price is $39 a month, flat, and it runs outside your monday.com account, so it spends none of the automation actions your plan includes.
Anything to know about monday.com?
The API is GraphQL and priced by complexity, so a big backfill arrives in steps rather than all at once, while day to day changes are immediate.
Anything to know about Jira?
This is for Jira Cloud. Server and Data Center use a different API and aren't covered here.
What if mine is a bit different?
Tell us what should go where in plain words. Small changes to the rules above are usually free; bigger ones we price the same day and build into the same account.
