You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We do a bit of both... with the Jira Power-up on Trello it enables us to:
Question for this thread - I recently added the Jira power up to Trello. It doesn't look like it updates the Jira info in the Trello card after you associate the Jira issue in Trello. Have you had any luck getting it to show updated priority, status, etc? For example, I had the card in Trello, added an existing Jira story to the Trello card, and then update the priority in Jira. If I refresh the Trello card, the updated priority doesn't show.
What sort of projects/teams would be in Jira? Its main use is for bug tracking/agile software project management, so it would work well if you have technical teams needing a solution to manage their work. You could use it for non-technical projects, but it is a reasonably heavy project management tool, so not all non-technical people find it easy to use.
What's the need to bring in another tool on top of Trello for project management? What features are you looking for?
We're currently using Mavenlink to manage our work as our projects are complex with many steps involving a large team. We'd like to move all of our business to the Atlassian community as we love Trello and want to sync with it somehow.
We're looking for everything from tasking, syncing of email, invoicing, analytics, time sheets for employees, understanding if projects are below/above budget... the whole shabang
Got it! I've worked with plenty of clients that use both Trello and Jira in their organization. One client I worked with used Trello predominantly for the creative teams, and Jira was for more technical teams. Trello worked well for teams who preferred a more user-friendly/visual tool, and Jira was used more by the devs. There was a lot of cross-department work that happened, so we implemented Unito to keep all the Trello/Jira teams in sync.
Jira worked well for projects that were more complex and had a lot of structure, so they needed quite advanced PM capabilities to plan projects/report/do post-mortems, etc. Jira is great for that - it's super powerful and customizable. However, some people hated using it because it did seem quite intimidating for the end-user, so they gave people the choice of using Jira or Trello to manage their tasks. So even if the main project was in Jira, someone (or even a whole team) could have their board in Trello and whatever updates they made in Trello would be reflected back in Jira so no information was lost. It was a pretty cool system!