We performed a comparison between JIRA Portfolio and OpenText Project and portfolio Management based on real PeerSpot user reviews.
Find out in this report how the two Enterprise Agile Planning Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."Has good analysis integration capabilities."
"I use it to plan and schedule the things I take care of. I can create and share a document if I want to discuss new ideas with my team remotely."
"Managing product development and managing inter-team communications are also valuable features."
"The most valuable feature for me is the visualization and organizing of the tasks. We can have a pick, and then we can stick the multiple issues under that, and then we can again have a sort of hierarchical installation, and that's very useful."
"The most valuable feature of the JIRA Portfolio is the many features it provides, such as code integration, documentation, roadmap, and Eclipse. The solution is useful for product managers."
"The documentation is very well done."
"The best features of JIRA are its flexibility and configurability, allowing us to tailor it to our specific needs."
"We have found the solution to be stable."
"The portfolio management and the resource management are the key features."
"Resource management: The resource management module is very complete and covers most of the time all needs of customers."
"I like the ease of customization from an admin perspective. I'm really excited about some of the things that are coming in version 10.0.3 as far as what admins are able to do."
"Micro Focus Project and Portfolio Management (PPM) has a very strong workflow engine."
"It is very important that the platform gives us a single place where we can measure progress toward goals, as we have weekly meetings with the CTO. We present these consolidated overviews and dashboards to him so that he has an overview of all the projects and can see the status of all the problems that we have and we are working on."
"Micro Focus PPM is flexible and easy to use. It's simple to customize and configure workflows."
"I like the automated calculations, especially on the resource side. When project managers enter their resource requirements into their staffing profiles, they are automatically translated into labor forecast calculations. PPM automates a significant portion of the forecast calculations. Timesheets are also built-in. We automatically process time sheets and bill them accordingly."
"Overall, they have a very strong workflow management capability. That's a very strong feature because then you can model any process easily. Whether it is a demand management process, a pipeline management process, or your project delivery methodology, it is much easier because of their workflow management capability."
"Our major team does not control or manage JIRA server well since sometimes there is trouble using the solution, which is a problem. The solution's speed needs to be improved."
"The query features should improve in JIRA Portfolio. For example, if I would have to create my own queries for looking into something such as what business features we have released last month, or the last three months, I don't know if I can do it. The solution requires a certain level of expertise."
"Another thing could be to have an easy way to manage the Portfolio and have more ways to share and to show graphics and reports"
"The reporting and dashboard capabilities have room for improvement."
"I think that front-end development is a little bit buggy in some cases. Some of the features take a while to respond and some need to be more clear."
"Requires some effort to insert functionalities and that could be simplified."
"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."
"Currently, HPE PPM does not allow “Project” approval, but only simple “Demand Request” approval (mobility)."
"They can make its UI better. Currently, the UI is a bit clunky."
"The user interface is very, very old and is missing some functions, such as, for example, re-do, follow, and share functions. The UI is not good."
"We had a couple of issues with stability or performance degradation about a year ago, around the time of the initial rollout. Since then, we've only had two unexpected outages that were quickly resolved."
"Portfolio scenarios: This is a very powerful feature. However, it’s limited to analyses."
"We constantly put in requests for some of the things we need. One of those is being able to export just our standard request type to PDF."
"I would also like to see improvement in PPM's reporting and alerts. PPM has reporting capabilities, including HTML reports and portlets. But a majority of clients will build their own reporting platforms, or they will use external reporting platforms like Tableau and QlikView."
"Sometimes features in PPM don't work as expected, or our users request a new feature. Typically, our partner vendor can deploy those changes. But there have been a few instances when we had to raise it with Micro Focus because it's beyond the ability of our partner vendor. When we raise the issue with Micro Focus, it sometimes takes time because it needs support from other customers using PPM, not just our bank. It goes through a voting system. Other customers need to vote for the feature. The features that get the most votes will possibly be added."
More OpenText Project and portfolio Management Pricing and Cost Advice →
JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 47 reviews while OpenText Project and portfolio Management is ranked 10th in Project Portfolio Management with 24 reviews. JIRA Portfolio is rated 8.2, while OpenText Project and portfolio Management is rated 7.8. 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 OpenText Project and portfolio Management writes "Gives management a cohesive place for tracking business strategies and goals, but cosmetic aspects need work". JIRA Portfolio is most compared with Jira Align, Oracle Primavera Portfolio Management, Microsoft Project Server, Adobe Workfront and Microsoft Azure DevOps, whereas OpenText Project and portfolio Management is most compared with Jira, Planview PPM Pro, Smartsheet and Teamwork . See our JIRA Portfolio vs. OpenText Project and portfolio Management report.
We monitor all Enterprise Agile Planning Tools 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.
