We performed a comparison between Adobe Workfront, Digité SwiftKanban, and Jira based on real PeerSpot user reviews.
Find out what your peers are saying about monday.com, Microsoft, Asana and others in Project Management Software."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 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."
"Monitoring the progress of projects and tasks is very effective."
"The solution is stable."
"The tool is very user-friendly."
"Feature-wise, I would say that its overall ability to be infinitely customizable is valuable...My experience with the support team has been amazing."
"The intake feature is the most valuable in Workfront."
"The reporting part is very good."
"It is easy to deploy in the cloud and other environments. It is also easy to view the reports of the sprint review or the sprint plan and the relation between the backlog and the repositories."
"The flexibility to create different flows is most valuable."
"Jira has a good reporting system. It also has an API, so we can do all sorts of reporting."
"The feature that I have found most valuable is its ease of use. I don't need to train anyone to use it, I just give them access and they can use it to add comments, move their issues, change the status, monitor, read, and so on."
"Overall, it is very intuitive. It is so lightweight and easy to use. It is easy to manage our product backlog and user stories, and it produces great reports."
"A stable solution with no unplanned downtime."
"I like seeing which tickets are open and what our response rate is. They have a lot of good metrics in their system to see what's going on."
"It's very simple to change the workflow and adapt it. Jira is very user friendly for the agent and the user."
"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."
"Workfront's reporting capabilities must be improved."
"Sometimes there are glitches when we are reviewing an interactive proof."
"I would say that the stability, honestly, has gone down since the Adobe acquisition, and the quality when they roll out their updates."
"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."
"We were having some difficulties creating different kinds of reports and dashboards."
"The interface can also be customized to fit and accept many tools for better performance and customer service improvement."
"Some of the reports could be automated."
"I don't know whether there is a Jira problem or a test risk problem, however, sometimes, we face issues on fetching the reports."
"It would be good if we can grant access based on the roles. This is something that Jira can look into. Currently, anyone with Jira access can access everything. Being able to define access based on the roles will give us more flexibility in managing Jira. I would like to have more reports in Jira. Currently, eight or nine reports are there. You can use Screen Test to get more reports or data from Jira, but you will have to get more add-ons, plug-ins, and stuff like that. It would be good if they can increase the number of reports."
"The challenge which I frequently see from Jira is the label. When you search for a label sometimes, it suddenly disappears. If there's a mismatch due to all-caps or lower case, you won't be able to find it. It won't even come up as a recommendation or suggestion. That's something that can be really frustrating, as people create labels in their own specific ways and then no one else can find anything."
"Could offer an improved user experience."
"We would like to see the integration of a lite-version of Confluence, just to manage some of the templates and documents."
"Something I do not like about the new version is that there is a need to browse all the way back to the beginning, should a person click on a task that is specifically for his group and wish to go back and look at the other portfolios or people."
"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."
"The reports in Jira can be improved, especially for test reports. I find it difficult to customize and integrate for different testing purposes."