What we do
Tools
Industries
Department
How we workLet's talk →
Home/Trello/Trello Jira Integration
Trello + Jira

Trello Jira Integration: What Trello Does Built In, and What It Leaves to You

Trello now has Jira features built in, replacing the old Jira Power-Up. You can attach Jira work items to cards, create a work item from a card, and fill a list from a Jira search. That covers linking. Keeping a planning board and an engineering backlog in step is a different job, and it's where most teams get stuck.

Create a Jira work item from a Trello card

On the card front, open the card menu and choose Create Jira work item. Or open the card and use the … menu.

Card … Create Jira work item

Check the form: site, space, work type and status are pre-filled. Change what you need and select Create. A Jira link card appears under your card, and the two are linked.

Copied across: card name to summary, description, reporter, attached links and due date. Attachments aren't copied. This runs in the Trello web app only, not the desktop apps, and not in Firefox or Safari.

Where the built-in link stops

Linking is solved. These are the complaints teams still have after setting it up.

The original card doesn’t follow the work item

How you'll know: Jira says Done, but your card is still in the In Progress list, so the board everyone else reads is wrong.

Fix: Atlassian's docs describe status on the link card, not moving your original card. If list position is how your team reads status, that move has to be synced.

Two comment threads about one piece of work

How you'll know: The requester asks a question on the Trello card. The engineer answers on the Jira item. Neither sees the other.

Fix: Pick one place for discussion and say so on the card, or sync comments between the two.

Fields that only exist on one side

How you'll know: Trello custom fields, labels or checklists that matter to your team never reach Jira, and Jira priority or sprint never comes back.

Fix: Decide which fields each team actually needs from the other, then map only those. Syncing everything creates noise.

Leadership wants one view across both

How you'll know: Someone exports both boards into a spreadsheet before every status meeting.

Fix: Build a combined report from the Trello and Jira APIs, or move the planning layer into one tool if the teams are willing.

Which built-in Jira feature fits the job

You want to Use Keep in mind
Show a Jira work item on an existing card Attach it to the card, or paste its link as a Smart Link Both show the work item's details and let you change its status from Trello. The card itself stays where it is.
Send a request from your board to engineering Create Jira work item from the card Attachments stay behind in Trello. Add screenshots to the Jira item directly if engineers need them.
See an engineering backlog on your Trello board A Jira list filled by a JQL query The list fills with link cards. Link cards don't carry checklists, comments, due dates or attachments of their own.
Create work items or add comments as part of a routine Trello automation connected to Jira Good for one-way pushes from Trello. Test what happens when the Jira side changes before relying on it.

Linked or synced?

Built-in linking

When each team keeps its own tool

  • Trello users need to see Jira status and change it now and then.
  • Requests go one way, from the board to engineering.
  • One team owns the conversation, the other just reads it.
Two-way sync

When both boards must stay true

  • The card has to move lists when the Jira work item changes.
  • Comments, fields or due dates must match on both sides.
  • Leadership reads one board and expects it to be current.

Start with the built-in features. If people still copy updates by hand after a month, you need a sync: a third-party sync app such as Unito, or one n-frames builds against both APIs when your field mapping or rules don't fit an app.

Questions people ask

Does Trello integrate with Jira officially?

Yes. Atlassian builds Jira features into Trello: attaching work items to cards, Smart Links, Jira lists filled by JQL, creating a work item from a card, and automations that create work items or add comments. These replaced the older Jira Power-Up. What they don't describe is a full two-way sync of cards and work items.

Can I migrate from Trello to Jira, or the other way around?

Yes, as a one-time move. Check Jira's own import options for Trello first, and third-party migration tools for anything they don't cover. A migration replaces one tool with the other. If both teams keep their tools, you want linking or a sync instead.

Why would a team run both instead of picking one?

Because the teams work differently. Marketing, ops or client teams like Trello's simple board. Engineering needs Jira's backlog, sprints and workflows. Forcing either team onto the other's tool often costs more than connecting the two.

Our setup works, but updates don't carry over between the two boards. Can that be fixed?

Yes. n-frames builds the sync for the specific updates that go missing, such as list moves when a work item changes status, comments in both directions, or due dates and owners, using the Trello and Jira APIs. We map only the fields each team needs.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.