We performed a comparison between Asana and JIRA Portfolio based on real PeerSpot user reviews.
Find out in this report how the two Project Management Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Asana is a very simple interface for project managers to figure out, providing all the functions they need."
"The solution scales well."
"The most valuable feature of Asana is the ease of navigation."
"Asana allows you to create your own project with sub sections with subtasks that can be assigned. The feature I really love is that you can tag people to notify them that there has been progress on a project as well as add attachments."
"It is very good for managing the timeline. I'm a quality manager, and I have different testing projects running with different work breakdown structures. Asana makes it very easy to implement and monitor the plans. It is easy to move the tasks and complete them, break them down, and assign them to people."
"What I like most about Asana is its simplicity. For example: we're not the only ones using it, and we onboard our customers to it, and normally, they have no questions."
"The solution appears to be quite stable."
"The most valuable feature of Asana is the tracking of comments and documents in one place."
"The solution includes good and fast notifications for other project team members."
"The dashboard is the most valuable feature. The user experience is very good, it's easy to use."
"The developers can simplify tasks and each one of them can undertake a task and then they continue with development. Our processes are more efficient and easier for our manager and developers to track them. Their work is more organized."
"Jira Portfolio is useful for tracking time and hours. It's easy to manage, create tickets, and change the status of delivery reports. It's not complicated."
"Its stability is very reliable."
"Portfolio's most valuable features are that it's user-friendly and customer-centric."
"The customized workflows we can define are very valuable. JIRA's private projects is very useful as well. There are also a lot of plugins that they provide."
"We have found the solution to be stable."
"The inbox feature can be a little overwhelming if you are working with Asana just from its project boards and only checking it periodically."
"In some instances, there were subtasks where more than one person needed to review it, but I could only assign it to one person. I would have to create a subtask under a subtask and then assign it to other people. This could be improved."
"The product's page is not user-friendly."
"Currently, there are only a few available options, but it would be helpful to have more control over the notifications received."
"Auto-shift is an essential feature for planning, but it's currently not there. It should have this feature so that when you move a task that depends on another task, the dates should be auto-shifted. For example, you have two tasks dependent on each other. When the parent task is moved or delayed, the child task should also be delayed, and the date should be shifted. When we have a very long timeline, it's very complex to go task by task and shift the dates on the task. Auto-shift is a fantastic and basic feature of project management, and having such a feature in Asana would make our lives much easier. If Asana added this feature, it would complete the suit and close the project management cycle because currently, there is a gap."
"For large teams, scalability should be improved."
"The documentation could be enhanced by incorporating more visually informative videos that demonstrate how to accomplish specific tasks. While Asana's community support is valuable for answering questions, finding precise answers often requires sifting through multiple posts. Having concise and explanatory videos would greatly improve the user experience. When searching on platforms like Google, there are many individuals sharing their approaches to using Asana. However, the information provided is often not directly applicable to one's specific needs. Therefore, it would be advantageous to have comprehensive video tutorials that address common user queries. This would provide a more efficient and intuitive way of accessing information, especially when it comes to learning how to navigate and utilize Asana's features effectively."
"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."
"The kanban board could also use some more filters. We just had a project where the deployment for Jira didn't have any ETA, and it's a requirement for the client. We accommodate a lot of issues on the board, so the workaround was to create boards by project, not client."
"When I want to embed Jira Portfolio in a complete HLI cycle, I'm missing things to evaluate my ethic into my value stream."
"It's got kind of a steep learning curve."
"Their interface is a little unique and I think that's partly because the core of the product has morphed into several sub-products, but the underlying architecture has stayed the same on all of them in that it was originally a help desk ticketing system. It's a very tech-focused product and that's fair given its origins, but if they really want to expand their community of users, then they're going to have to move beyond that a little bit and polish it up."
"There is room for improvement in terms of scalability."
"Portfolio is easy to scale, but we've had some difficulties with it regarding compliance and support."
"We would love to be able to have direct contact with Atlassian. Currently, they are not working directly with West African countries. We are considering using JIRA Align, but when we contact them, they say that as we are in West Africa, they don't directly work with West Africa."
"The query features should improve in JIRA Portfolio. For example, if I would have to create my own queries for looking into something such as what business features we have released last month, or the last three months, I don't know if I can do it. The solution requires a certain level of expertise."
Asana is ranked 3rd in Project Management Software with 43 reviews while JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 46 reviews. Asana is rated 8.4, while JIRA Portfolio is rated 8.0. The top reviewer of Asana writes "Stands out with portfolios, easy setup, and real-time information, but needs big improvement when it comes to workflows, automation, and dashboards". On the other hand, the top reviewer of JIRA Portfolio writes "Powerful, flexible solution with a bit of a learning curve". Asana is most compared with Microsoft Project, Wrike, Microsoft Azure DevOps, monday.com and Jira, whereas JIRA Portfolio is most compared with Jira Align, Oracle Primavera Portfolio Management, Microsoft Project Server, Adobe Workfront and Planview AgilePlace. See our Asana vs. JIRA Portfolio 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.
