We performed a comparison between JIRA Portfolio and Zoho Projects 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 integration is very good. We've more or less integrated with everything including reporting and registering."
"The way to manage cards as a KANBAN, is really easy but when you need to track hundreds of projects, you need to be very clear in which way the things must be completed."
"The most valuable feature is the dashboard where we can see all of our projects and apply filters to shortlist those projects."
"The dashboard is the most valuable feature. The user experience is very good, it's easy to use."
"The solution includes good and fast notifications for other project team members."
"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."
"Has many functionalities including good supervision and workflows."
"The most valuable feature of JIRA Portfolio is the visuals it provides rather than Kanban boarded tickets."
"We use the tool for our core business project. If we have a new site coming up, there are many milestones that need to be checked. The solution helps to ensure consistency."
"It is a scalable solution."
"The product is very easy to understand."
"It's easy for a user with a technical background to set up Zoho Projects on their own."
"The most valuable feature of Zoho Projects is all integrated into one. We don't have to start using multiple tools, such as Projects, CRM, Marketing, Automation, Finance, and setting up Meetings. It's all in one solution. I don't have to go to multiple different platforms to have all the features I need."
"While integrating a voice solution with Zoho Projects, the focus was on creating a unified interface for voice and customer engagement across various platforms like Facebook, social media, and emails. The primary goal was to seamlessly merge the two platforms into a single interface. To achieve this, we engaged in API integrations and worked on aspects such as initializing, authentication, and access control."
"Timesheets and the ability to add attachments are very valuable features to us."
"We were able to track each department's work and what they were doing inside the actual department. Gantt charts are useful to track departmental progress and operation, or we are that item stuff."
"The kanban board could also use some more filters. We just had a project where the deployment for Jira didn't have any ETA, and it's a requirement for the client. We accommodate a lot of issues on the board, so the workaround was to create boards by project, not client."
"I think their view needs to be more user friendly. The UI makes it difficult to find things. Secondly, the configuration is very complex. JIRA should help people find out what configuration they are using."
"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."
"The team-centric view is slightly weaker in JIRA compared to its competitors, especially considering how I can evaluate how each resource has been placed, not just in one project but across JIRA."
"Requires some effort to insert functionalities and that could be simplified."
"When I want to embed Jira Portfolio in a complete HLI cycle, I'm missing things to evaluate my ethic into my value stream."
"We are using the on-premise deployment, but it is slower and not as easy to manage as the cloud version."
"JIRA Portfolio's configuration management could be improved."
"Zoho Projects' time log addition part can be improved."
"The tool should add live chat, live call, and live meeting features where clients can communicate."
"Sometimes the solution does not work."
"The solution should improve on integration and customization."
"Its template management feature could be easier to use."
"The UI and UX must be improved."
"The solution’s interface should be improved."
"It is not easy to drag and drop a task from one person to the other. I think the resolution for the issue is work in progress. The product's stability can be improved."
JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 47 reviews while Zoho Projects is ranked 14th in Project Management Software with 14 reviews. JIRA Portfolio is rated 8.2, while Zoho Projects is rated 8.0. 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 Zoho Projects writes "A scalable solution with great features that enable efficient collaboration". JIRA Portfolio is most compared with Jira Align, Oracle Primavera Portfolio Management, Microsoft Project Server, Adobe Workfront and Microsoft Azure DevOps, whereas Zoho Projects is most compared with Trello and monday.com. See our JIRA Portfolio vs. Zoho Projects 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.
