We performed a comparison between Jira, Planview Daptiv, and Wrike based on real PeerSpot user reviews.
Find out what your peers are saying about monday.com, Broadcom, ServiceNow and others in Project Portfolio Management."The most valuable features are the customized Dashboard, Sprint Planning, and Automatic Notifications."
"The most valuable feature is that it has different APIs available, with good services, and it is completely by the books."
"We like team collaboration and cross-functional collaboration."
"Issue linking has enabled teams to trace issues."
"It was easy to use. The consultants that we had on board were familiar with it. So, obviously, having a community that had used it before or was familiar with it was a positive thing."
"Great for tracking my development team's productivity."
"The traceability mapping feature is something that became very useful, especially during releases and bug fixes."
"The features that we find most valuable are the Workflow, Scrum workflow, and Dashboards."
"The powerful collaboration is definitely the most valuable and the fact that you can adjust flexibility to almost any methodology, and the easy creation of complete new functionalities without programming code."
"Changepoint gives us a view of the project status and needs very clearly, which are things that we used to miss with MS Project and Excel."
"It's difficult to pinpoint just one most valuable feature, as there are many features that can be beneficial. For the specific use case of my client's project management office, they found the project management features of the application to be particularly valuable, such as project boards, reporting, and the ability to customize views. Additionally, task management and project scheduling were also highly utilized. However, capacity planning was not used as much as the others, as there was a lack of support from executives to invest in training and implementing it due to a lack of processes in place. The project planning features, dashboard, and reporting capabilities were considered the most valuable."
"The timekeeping features are great and very helpful."
"I like the reporting engine, IBM Cognos, especially the analytics. That's a good tool. It's quite strong on the ideation and capacity-planning side, which is a huge plus."
"The solution is stable and reliable."
"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."
"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."
"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."
"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."
"Visibility and organization are the most valuable features of Wrike."
"We utilize time tracking and reports most often."
"If I'm comparing it to ALM Octane, the documentation is not as robust as ALM Octane's documentation. So, they can improve on the documentation side."
"Adding applications is very expensive."
"Jira could improve by making the user interface easier to use and the functionality could be better. While we are managing multiple sprints and other elements of the projects, it's very difficult to manage the labels and other aspects."
"While it's very powerful, it's very complex sometimes."
"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."
"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."
"I want the tool to integrate connectors."
"Based on the feedback from my admin, it is sometimes difficult to find some of the features. It is not a big deal, but its configuration interface can be improved to make it easy to find things."
"Expense management, simulation scenarios, and budget control could be great and useful features to include."
"The areas that should be improved in Planview Daptiv are a subject that can be viewed differently depending on who you ask. I feel they should focus on excelling in one specific area rather than providing average capabilities in many areas. For example, their project planning software is satisfactory but not as advanced as Microsoft Projects. The same goes for the capacity planning tool and reporting capabilities, which can be improved upon by using custom Excel spreadsheets or by hiring a business analyst for additional support. In short, the biggest weakness of Daptiv is that it does not excel in any one area and only provides average performance."
"I find the solution has an excessive amount of features. Many aren't even kept current. Some aren't useful at all. There's an overall lack of coherence within the solution. It can make the execution difficult. Many features can easily be eliminated and it would help streamline the solution. They should get rid of 80% of the features and then really focus on the leftover 20% to make it a really great product."
"It would also be nice to see some improvements on the IBM Cognos Analytics. There's still work to be done on the analytics side of things, like your condition formality."
"This solution needs more standard connectors to other solutions."
"The response from the website is a little bit slow, and the tool is too expensive for a small team."
"Wrike needs to be more responsive to community requests for new features."
"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."
"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."
"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."
"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."