We compared Asana and Jira based on our users reviews in six parameters. After reading the collected data, you can find our conclusion below:
Asana's setup process was considered simple and easy, requiring minimal training. In contrast, the setup for Jira had mixed opinions, with some finding it straightforward and others finding it more challenging.
Asana is known for its efficient project and task sharing among team members, while Jira is recognized for its user-friendly interface. Asana offers extensive customization and effective task management, while Jira provides flexibility and customization choices.
Both Asana and Jira have areas that can be enhanced. Asana could improve scalability for larger teams, offer more user training resources, enhance integration with other workflows, provide customization options, and simplify the user interface. On the other hand, Jira needs improvements in compatibility with Microsoft Word, export options, user interface and experience, customization options, reporting and tracking features, integration with other platforms, documentation, workflows, and permissions management.
Asana and Jira have varying setup costs according to users. Asana is considered reasonably priced, while Jira's affordability is a matter of mixed opinions. Asana does not have any undisclosed expenses and adds users in groups of five, whereas Jira's pricing and billing system is transparent.
Asana users have experienced positive outcomes in terms of time investment, productivity, and business growth, resulting in a favorable return on investment. On the other hand, Jira users have not yet determined their ROI, but instead emphasize qualitative advantages and the importance of organizational structure.
The feedback on customer service and support for Asana and Jira is varied. Asana users express dissatisfaction with the absence of a supportive community and slow response times. On the other hand, Jira users highlight the necessity for better technical support and complain about receiving irrelevant responses.
Comparison Results
Asana is highly praised for its user-friendly setup and ease of use. Users appreciate its ability to share projects and tasks among team members, as well as its high level of customization and task management capabilities. The real-time updates are also a valuable feature. However, there is room for improvement in terms of scalability, integration with other workflows, and customization options. On the other hand, Jira's setup complexity varies, but it is valued for its user-friendly interface and customization options. Users appreciate its integration with other Atlassian products. However, there are areas for improvement, such as compatibility with Microsoft Word, better UI/UX, more customization options, and enhanced reporting features. Opinions on pricing vary for both products. Asana users appreciate its basic solutions, while Jira users find it comprehensive. Customer support for both products has mixed reviews.
"I love the way it monitors all of the current and past projects, and it sends notifications to keep everything on the track."
"The ability to share projects and tasks among team members appears to be the most valuable feature."
"Asana has significantly reduced the number of emails we exchange because we can access the project directly. It organizes all the tasks related to each project, assigns them to staff with due dates, and tracks progress."
"Stable Kanban style tool for collaboration and task management. It runs smoothly and has a straightforward setup."
"I really enjoy the portfolios in Asana. One of the ways Asana stands out to me is with portfolios. You can have all your different projects, and you can have those assigned to different teams. If you want to customize a grouping of projects, you can use portfolios. For instance, one of the things that we do is we can assign a portfolio to a specific strategic objective we have, and we can put all those projects that are related to that strategic objective in that portfolio. We then know exactly what people are working on to help us achieve our goals. So, I really like portfolios."
"The solution scales well."
"The general UI shows progress and data analytics for all projects in progress."
"It has helped our departments maintain visibility."
"The dashboards are useful."
"Powerful features including a good reporting capability."
"This solution focuses on lean methodology which we have found useful and it can also be used on any device."
"The most valuable feature is that it has different APIs available, with good services, and it is completely by the books."
"It's really smart how they connected third-party vendors into their own marketplace. You can create and add apps. Anybody can do it."
"The user story map is excellent. The features can be composed into stories and they can be allocated to each of the sprints in a program increment. It allows you to see all that in the user story map, and you have various dashboards to see the stories in various views. You can see them as a backlog view, for example, or you can see as an actual sprint view."
"The solution's most valuable features revolve around the dashboard view, which has a burndown chart indicating progress."
"It allows you to do a lot of stuff, and the functionality is pretty rich. It integrates well with other products, like GitLab, that we are currently intensely using at the company."
"Currently, there are only a few available options, but it would be helpful to have more control over the notifications received."
"It would be beneficial if Asana had a predecessor feature that automatically adjusts all subsequent dates when changes are made to a timeline. For example, if I assign a designer four hours for one task and two days for another, and the completion of a task takes longer than anticipated, it would be convenient if updating one date could prompt the adjustment of all other relevant dates. Essentially, this feature would streamline the process and eliminate the need for manual adjustments."
"The documentation for integration could be improved. We require more information to facilitate the integrations."
"We have not used Asana on our private server. We have been using the cloud solution. We need an on premise solution for government agencies."
"A user should be able to identify an assignee for specific tasks or task types while applying the template, or at a minimum, allow for a default assignee. As it is, the template gets created with the just task dates driven by the project start and end dates inputted by the user. In my current situation, I'm assigning myself to many tasks, so I have to do that manually every time. Even if I eventually start adding other people to assign tasks, there won't be more than a handful to do. However, those few people will have multiple tasks. It would be nice to be able to select those individuals during the setup rather than having to do so manually once the project has been created."
"There could be some improvements in terms of how projects or day-to-day work is organized. One of the challenges when it comes to rolling out to an enterprise is the way the projects are organized. It has a kind of setup where you have different projects and tasks, but it is not as organized as Smartsheet when it comes to organizing projects or different teams. It can get really cluttered really fast. JIRA has another suite to submit the support tickets. It would be good if Asana could branch out to incorporate some kind of workflow. It is great for collaboration and recording work, but there isn't any workflow. It would be useful if they can map out a workflow of who approves what. This is kind of a big ask, and it is not geared towards that."
"This solution has a learning curve, where it is initially difficult to use."
"You need to have an action plan, otherwise, it won't be as effective."
"It should be connected to ServiceNow."
"The reporting needs to be improved."
"It is not capturing the number of hours for which each person has worked on certain things. We use many add-ons to let resources enter the time in the user story itself. We use an add-on called Tempo, but it is kind of a lousy add-on. It is not straightforward. Rather than helping us, it creates a lot of confusion. So, instead of looking out for the additional add-on, I would prefer to have the timesheet entered as a part of Jira itself. They are anyways capturing every information they could for each user story, and then we are able to break down all the task lists. For each task, we're also assigning a resource. So, while we're doing it, why can't they allow the users to enter the time that can be created as a report? Right now, we need to acquire the add-on, and the add-on is not great. It is not helping. The add-on is also not free."
"it would be helpful to have a better tutorial for learning and to have a better understanding of what the features are and what they do."
"I struggle with Epics, how they are implemented in JIRA, because they don't work like any other Story, I see a list of Epics, but although I can order them, there are some mismatches with how the Epics are used compared to what Scrum expects, or what Story mapping expects an Epic to be."
"There needs to be an easier way to capture a few metrics. I wish there was an easy way for Jira to explain to me what has been added after the sprint has been done. Currently, it is a bit difficult for me to tell. In addition, when rolling over stories from one sprint to another, it is kind of difficult for me to find out how many story points were actually rolled over without going into Jira and doing an analysis. I wish Jira would somehow aggregate that information for me so I can easily report about it."
"End-to-end management from product backlog to test completion could be improved."
"Pretty much 70% - 80% of the Next-Gen Projects features are still to be developed."
Asana is ranked 3rd in Project Management Software with 43 reviews while Jira is ranked 4th in Project Management Software with 266 reviews. Asana is rated 8.4, while Jira is rated 8.2. The top reviewer of Asana writes "Extremely stable, user-friendly, and easy to navigate". On the other hand, the top reviewer of Jira writes "A great centralized tool that has a good agile framework and is useful for day-to-day planning, task management, and work log efficacy". Asana is most compared with Microsoft Azure DevOps, Microsoft Project, Wrike, monday.com and Trello, whereas Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and Polarion ALM. See our Asana vs. Jira report.
See our list of best Project Management Software vendors.
We monitor all Project Management Software reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.