We performed a comparison between JIRA Portfolio and Wrike 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."The most valuable feature for me is the visualization and organizing of the tasks. We can have a pick, and then we can stick the multiple issues under that, and then we can again have a sort of hierarchical installation, and that's very useful."
"The most valuable feature of the JIRA Portfolio is the many features it provides, such as code integration, documentation, roadmap, and Eclipse. The solution is useful for product managers."
"The initial setup is simple."
"Has good analysis integration capabilities."
"The solution is very powerful and the underlying structure of it is well done. The company behind the solution is very open as far as their whole ecosystem is concerned. They also do a lot of work in the training area."
"The solution is very stable."
"The solution is stable and reliable."
"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 can easily write down the tasks and reorganize them as well as have a progression index. Wrike offers several views including a kanban view and Gantt chart view."
"It's a very easy-to-use and flexible tool. We can easily write and create queues for different themes. It's very user-friendly."
"The solution is stable and reliable."
"This is a good tool for project progress tracking and sharing tasks with internal and external parties."
"The most valuable feature of Wrike is the tag functionality."
"In our company, we heavily rely on Wrike. Wrike has helped in communication, managing all sorts of projects and tasks, and having a history of all our correspondence items."
"The product is intuitive. It is easy to learn and update. You can follow the project from the beginning till the end with the help of the solution. The tool helps to update the project in seconds."
"We utilize time tracking and reports most often."
"I think that front-end development is a little bit buggy in some cases. Some of the features take a while to respond and some need to be more clear."
"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."
"In the next release, Portfolio should include more metrics and develop their portfolio planning."
"I think the solution can improve in graphs and the analysis part."
"JIRA Portfolio could improve new implementation because if I want integration for the complete wide frame tools it cannot provide any wide frame tools."
"JIRA and Confluence must be linked automatically."
"If you want to generate a report for individual usage, it's difficult."
"We had to use assistance for the initial setup."
"We faced an issue with the Wrike outlook add-on; it is only available for Microsoft Office 365, and not the on-premise version."
"Wrike needs to be more responsive to community requests for new features."
"The response from the website is a little bit slow, and the tool is too expensive for a small team."
"On one side, it's very easy to create a task with text, but on the other side, it's not very well-formatted. Therefore, it's difficult to track specific data written in a task. We are making templates, but it's not enough to use a template to know the exact status of different tasks. One thing that we are looking for in Wrike is a better workflow. Because we can only move the status of tasks, we can't really manage workflow and send a task to a specific person. This is what is really missing in Wrike as compared to other tools. We are looking to replace Wrike because we need support for workflow. Another issue with Wrike is that they bring a lot of versions of the tool, which it's not so easy. They bring new versions very frequently, and these versions look similar. For example, we are using robots to read the tasks in the tools, which is problematic with Wrike because it is changing very frequently."
"This solution could be improved if we were able to better analyze how the application consumes cloud resources as this can cause a delay in performance."
"The product needs to send direct emails to customers updating the latest aspects since it is better to hear directly."
"It would be great if they could develop more reporting."
"What annoys me with Wrike and things that I would like to improve is that you need to have a very organized workflow that everyone in the company follows, and only then will Wrike work."
JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 47 reviews while Wrike is ranked 7th in Project Management Software with 58 reviews. JIRA Portfolio is rated 8.2, while Wrike is rated 8.6. The top reviewer of JIRA Portfolio writes "Powerful, flexible solution with a bit of a learning curve". On the other hand, the top reviewer of Wrike writes "Convenient Tool for Project and Task Management, comes with extra features including Analytics and Reporting ". JIRA Portfolio is most compared with Jira Align, Oracle Primavera Portfolio Management, Microsoft Project Server, Adobe Workfront and Microsoft Azure DevOps, whereas Wrike is most compared with Asana, monday.com, Adobe Workfront, Trello and Jira. See our JIRA Portfolio vs. Wrike 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.