We performed a comparison between Jira 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."It was very easy to learn Jira. As a scrum master, I run daily stand-ups, and they are run directly from Jira. The feature that I really love in Jira is called Issue Navigator. It allows me to customize how I want to show the user stories within Jira to my squad."
"The configurable workflows and boards make it easy for us to execute and oversee our own unique process."
"It provides very good visibility and traceability. You can clearly see each and every part of a process. It is also user-friendly and robust. It is working well, and there are a lot of add-ons or plug-ins out there that you can use."
"It is a very convenient tool. We can organize our sprints through scrum or kanban. There are scrum boards, and there are kanban boards. If you prefer scrum, you can use Jira. If you prefer kanban, you can still use Jira. You can create your kanban boards in a similar way as you create your scrum boards. It is very useful. It also seems to be very popular these days."
"We use it for capacity planning. We need to gauge and assess whatever is coming to our pipeline and then everything comes to the pipeline, appears as a pic, and then based on that, we create the story points and we take it from there."
"The solution is extremely stable."
"Internally we use Jira for our own implementations and capturing requirements and our customers are using the whole tool for the whole software development life cycle. They're using it for the full life cycle of the product."
"The most valuable feature is working with sprints and having the ability to create sprints."
"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."
"Visibility and organization are the most valuable features of Wrike."
"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."
"The solution is stable and reliable."
"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."
"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."
"We utilize time tracking and reports most often."
"We would like to see integration between Tempo and Jira."
"The GUI should have much better features like more graphical illustrations. There are some cases or benchmarks that we are trying to capture into a dashboard GUI's graphical summary, but unfortunately JIRA is not able to do that."
"Jira can improve by making user management better. It is not easy to have visibility of who has the right to do what. Only the administrator has this visibility but there should be the option for other users too."
"Atlassian has multiple tools and it becomes difficult for a customer to process everything differently. Atlassian should combine them and form a single solution for DevOps by including the Jira Confluence, Bitbucket, Bamboo, and others. This would be much easier for customers by purchasing a package, rather than purchasing bits and pieces. With Azure DevOps and other companies, it becomes easier to go with one company having multiple areas that they can cater to, but in Atlassian, the problem is that you have to select different solutions to have a full package. For example, to have document management customers have to purchase Confluence and for Git repository management they have to purchase Bitbucket, et cetera. There is always another add-on that you need to attach to have a complete solution in Jira."
"Jira could provide more insight into sprints such as how did we perform in the last sprint compared to other sprints. It would be helpful to have metrics and a dashboard feature for others to see."
"There are a limited number of gadgets accessible in Jira; thus, additional ones should be supported."
"There should be a way to look for specific comments. When we have thousands of comments on a Jira ticket, there is no way to look at the comments of a specific type. In the comments, if there is a way to put a tag, it would be helpful. For example, when there are a lot of lengthy discussions happening on a particular ticket, there could be a conclusion tag or something like that to indicate a conclusion. It would help in sorting the comments based on a certain category, such as conclusion."
"Although it covers the overall requirements and measurements, it'll help if they had their own test execution feature."
"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."
"We feel that the actual project reports and roll-ups could be a lot different. We are seeking something more for the dashboard. We would like a high-level dashboard that can be broken down into individual product roll-ups and tasks that are assigned. If you assign someone to a task, it assigns them all of the tasks under that. We want to be able to break those down so that a person doesn't have an 800 task list, for example. We want more separation with that and a higher-level dashboard experience."
"It would be great if they could develop more reporting."
"Wrike needs to be more responsive to community requests for new features."
"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."
"We faced an issue with the Wrike outlook add-on; it is only available for Microsoft Office 365, and not the on-premise version."
"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 is ranked 5th in Project Management Software with 243 reviews while Wrike is ranked 7th in Project Management Software with 58 reviews. Jira is rated 8.0, while Wrike is rated 8.6. 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". 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 is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Polarion ALM and Rally Software, whereas Wrike is most compared with Asana, monday.com, Adobe Workfront, Trello and Microsoft Project. See our Jira 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.