We performed a comparison between Jira and Planview Portfolios based on real PeerSpot user reviews.
Find out in this report how the two Project Portfolio Management solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Jira has a good reporting system. It also has an API, so we can do all sorts of reporting."
"We integrate Jira with QRadar which is helpful."
"When combining Jira with Bitbucket, you have the possibility to ensure continuous integration and other functions which is highly appreciated by our software development team."
"The scalability is good."
"The pricing of the product is very good. It's not too expensive"
"The most valuable feature is the full integration between Work management, Source code management, and Test Automation."
"It also works well with all the integrated tools that you buy."
"The most valuable features are that it is good for tracking the issues and it provides for the usage of Confluence."
"Enterprise One provides end-to-end work management for the full spectrum of types of work in one tool. It affects our project management because our project management uses Planview to monitor their daily work. Every night it loads our SAP system and then they monitor the daily work. They use Planview as a full planning and monitoring tool."
"We provided whatever feedback we had to the Planview team, and they went in and built those additional features that we requested. For example, they created a great way for our users to search for a specific resource, project, program, or role. We were not using some of the features, and we wanted them to not be visible, and they helped us with that. They also brought a feature to provide visibility into when a resource was never assigned to any task. There was no visibility to this before. This feature was really very good for visibility into the resource portfolio."
"Enterprise One provides end-to-end work management for the full spectrum of types of work in one tool."
"It maps back to our SDLC process pretty well. I'm able to see the stage of where things are at. We also use Azure DevOps for all of our requirements and our coding."
"The overall interface is very easy to use. It puts together strategy and execution across all your investments."
"The most valuable features are the control and visibility that you have for portfolio management in terms of projects and capacity planning for resources along with strategies and outcomes, etc. It's so easy to access information for sharing analytics and reporting."
"Whenever we have issues, there is always someone ready to help us. Their people are knowledgeable and responsive. They get to tickets quickly. Just three or four weeks ago, we were having issues with getting data into Planview. We submitted a ticket and the turnaround was probably 45 minutes to get a response."
"The Kanban board has really helped us be more agile and we can keep track of everything that is ongoing."
"Out-of-the-box reporting is limited. It would be helpful if more customisation was possible."
"I would love to have more features to make nice documents, like Release Notes or a feature overview, right from JIRA."
"In the way it is deployed, I think Jira is too dependent on the third-party applications that are available in its marketplace. If we could get some of the basic functionalities which are offered by these third-party applications, that would be ideal because each time we need a new functionality, we have to purchase a new plugin as an add-on."
"The way to configure it can definitely be improved. It is very difficult and complex to configure. Its configuration should be simplified."
"I'm mostly focusing on the requirements traceability with my thesis, the integration could improve for other tools. The companies are not only using Jira. For example, for the test cases or for the documents templates, we are using Polarion and we have been having some integration issues."
"Jira could improve the workflow, screen, and field configurability. They are lagging behind other solutions, such as Allegra in work system configurability."
"The hierarchy for Jira tickets is too flat."
"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."
"There can be improvement on the sense of urgency because a lot of times we've exhausted everything that we can, and now, we're reaching out. So, it isn't a, "Well, have you tried to reboot this?" We've already done everything. Once we put in a ticket, there should be more of a sense of urgency on it."
"Sometimes within the application, when you pull a report, it takes awhile performance-wise for the reports to pull up."
"We have almost like a third-party group who has to do a lot of our configurations. It's a bit painful for us anytime we want to make a change. The other issue is that we have different groups all in the same instance. So, if one group wants to make a change, it impacts everyone. Then, we all have to come together, to say, "Yes, we approve this change, or no, we do not." Thus, it has not been as flexible for us."
"When it comes to reporting there are some challenges with integration."
"The financial piece of the tool could be better. While it may have to do with the complexity of the work that we do, it seems that the tool should be able to drill down a bit deeper into the financial area."
"Being the IT development manager who implements the upgrades for Planview, I would love to see more thorough testing of expenditures and more thorough testing in general. When we do an upgrade, we have to do quite a bit of testing because we can affect the bottom line."
"One big issue we have been having during our annual planning is that only the creator of a portfolio can edit it. This means that only the creator of a portfolio can edit which projects are included or excluded in it."
"The content management definitely needs to improve. We don't really use content management for projects inside Enterprise One. We have actually switched to a SharePoint site. We have a feed from Enterprise One every night of all the projects that are created."
Jira is ranked 2nd in Application Lifecycle Management (ALM) Suites with 257 reviews while Planview Portfolios is ranked 8th in Project Portfolio Management with 63 reviews. Jira is rated 8.2, while Planview Portfolios is rated 8.0. 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 Planview Portfolios writes "Helps prioritize projects, share the big picture with management, and has a great planning capacity". Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and Polarion ALM, whereas Planview Portfolios is most compared with Broadcom Clarity , Planview PPM Pro, LeanIX, SAP Portfolio and Project Management and Adobe Workfront. See our Jira vs. Planview Portfolios report.
See our list of best Project Portfolio Management vendors and best Project Management Software vendors.
We monitor all Project Portfolio Management 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.
