We performed a comparison between Adobe Workfront, Jira, and Wrike based on real PeerSpot user reviews.
Find out what your peers are saying about monday.com, Microsoft, Asana and others in Project Management Software."The tool is very user-friendly."
"The intake feature is the most valuable in Workfront."
"I also like Workfront's integration. The solution integrates natively with other systems. It's easy to connect Workfront to any product that has a customer service database, such as a CRM or service ticket management solution."
"Feature-wise, I would say that its overall ability to be infinitely customizable is valuable...My experience with the support team has been amazing."
"Monitoring the progress of projects and tasks is very effective."
"The solution is stable."
"Workfront is innovative and these were plenty of features that I found valuable while working at Logitech. Workfront had this feature of Project Schedule Templatization. This saves time and effort and even leads to the standardization of processes that are well-assorted. The Intelligent Graphical Interfaces of Workfront allow one to look at a specific type of resource and a specific phase for a specific family of products. You can get quite granular with the data and even zoom in or out of the timeline. It also categorizes projects according to classes and portfolios so that over time, you can more easily understand what are the various metrics involved in producing a specific portfolio Another important feature is Workfront allowing you to validate milestones and investigate the project. This also helped me to understand which projects are performing well and whether it was beneficial to invest in the same. The IT and the app configuration is quite secure and it is one of the benefits. One more valuable feature is the integration of communication systems inside Workfront. This helps you differentiate between normal business emails and project-specific conversations. This is also known as ‘queues’ and I absolutely find this feature extremely powerful."
"I can say it is a powerful tool. We have everything in-house in that tool, like, creating reports, dashboards, creating various workflows, and everything we have inside one application."
"I've never had a bug or a bug message that I needed to open a ticket for."
"I was able to do real-time reports myself without having to wait for data import."
"The burndown chart is also helpful when it comes to reporting and allows us to know where we are going, especially during development."
"The solution provides users with clarity in terms of the scope of work in a given timeframe."
"It's flexible and it can provide a lot of different options, such as dashboards, that you can create and manage."
"I like that Jira allows you to customize the flow for an agile process and adapt it to your own flow."
"The timeline management is great."
"I think one of the most powerful features in Jira is the customization of fields and workflow."
"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 most valuable feature of Wrike is the tag functionality."
"Visibility and organization are the most valuable features of Wrike."
"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."
"This is a good tool for project progress tracking and sharing tasks with internal and external parties."
"We utilize time tracking and reports most often."
"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."
"The solution's visualization feature could be user-friendly."
"Our product and graphic designers are working with various Adobe products, but Workfront has a no-frills interface. It's a useful tool with everything we need, but it could be a little more attractive and present information in a polished way. It's a web interface, so it's accessible, but the appearance could be a little slicker."
"I would say that the stability, honestly, has gone down since the Adobe acquisition, and the quality when they roll out their updates."
"The interface can also be customized to fit and accept many tools for better performance and customer service improvement."
"Sometimes there are glitches when we are reviewing an interactive proof."
"Workfront's reporting capabilities must be improved."
"I have used the product and instantiated it, almost seven years back. The process was fairly complex, however, I don't know if they have changed the same now. But this is something I think, if not addressed can be improved. Another area that needs a little attention, is the change of implementation lead. Back when we had Workfront instantiated, we often had our timeline delayed due to the change in the implementation lead. Now Workfront is under Adobe and, in case, this issue, isn't fixed it should be given due attention. Also, Workfront is a universal tool, which can pose a difficulty for small businesses and companies, who don't have the required time, effort, and knowledge to configure it periodically."
"We were having some difficulties creating different kinds of reports and dashboards."
"One thing that I don't like about Jira is that when you do an export, it only allows a thousand issues. So the export feature needs to be better."
"The only thing that JIRA doesn't for us is release management in a way that I can create a list of versions easily."
"Sometimes it takes time to load the data."
"It should have its own repository for test case creation, so that one does not have to resort to third-party tools and plugins."
"The filtration could be better."
"Pretty much 70% - 80% of the Next-Gen Projects features are still to be developed."
"The hierarchy for Jira tickets is too flat."
"I don't know whether there is a Jira problem or a test risk problem, however, sometimes, we face issues on fetching the reports."
"We faced an issue with the Wrike outlook add-on; it is only available for Microsoft Office 365, and not the on-premise version."
"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."
"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."
"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."
"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."
"Wrike needs to be more responsive to community requests for new features."
