Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Syncing Jira Issue ID to Trello cards


I am looking into syncing trello & Jira. More specifically, I want to automatically create a JIRA issue when a Trello card in a certain Trello board is moved to a list/stage in that list.

When the JIRA issue is created, I want to sync the given JIRA issue ID back to the trello card from which the issue was created. When the card is updated in JIRA, I want to sync more of the information back to the Trello card so that uses can see the status of the card in JIRA (I.e. stage, planned delivery date, status, etc).

Anyone know how/if this can be done, for example by using the "Trello sync for Jira" by Intenso, Zapier, or similar services?

Thanks in advance for all tips and advice. 

2 answers

Is there an ability to move the trello card to another list, if the issue status in Jira changed? 

I tried the Trello sync for Jira" app but I can't get Jira and Trello to sync properly. Anyone else have it working?

Hello Jose,

Have you tried it again? We've got a couple of updates and fixes to the app in the meantime.

Even if you eventually gave it up, I'd appreciate that you share more information on what exactly was wrong, so we could fix it, if we didn't earlier.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events