We performed a comparison between Jira and OpenText Project and portfolio Management 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."We use Jira mostly for task coordination and assignment. Additionally, scrum methodologies defined work items and bug issues. If we create any bugs all of them are fixed."
"Offers a common language set so we can bring people into projects and get them up and running almost immediately."
"The links between tickets are very valuable and the boards I found to be configurable and usable. The boards allow some level of extended configuration and they can be customized according to our project needs. Additionally, it is easy to use."
"The solution's most valuable features revolve around the dashboard view, which has a burndown chart indicating progress."
"This tool can be used anywhere and on any device."
"The product provides high flexibility to create new workflows quickly."
"It provides very good visibility and traceability. You can clearly see each and every part of a process. It is also user-friendly and robust. It is working well, and there are a lot of add-ons or plug-ins out there that you can use."
"It improved communication, as it was a popular tool, and most people enjoyed using it."
"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."
"There are so many different pieces of functionality, and we use almost every single piece from deployment to demand, project, resource, and time management."
"Resource management: The resource management module is very complete and covers most of the time all needs of customers."
"Scenario comparison is the feature most valuable to us and the reason why we decided to choose HPE PPM over other portfolio management products."
"The portfolio management and the resource management are the key features."
"Recent Program Management lifecycle, Program Management aggregation views due to interactive UI (selection of risks, issues, and changes in Program Overview) and “flash look & feel" of this functional chunk, which is different in comparison to other parts of HPE PPM."
"The data provided by PPM is trusted and is available almost immediately; without trusted data there is very less scope of any tool to be successful."
"Has a powerful workflow engine that allows creation of workflow complexities and processes."
"I struggle with Epics, how they are implemented in JIRA, because they don't work like any other Story, I see a list of Epics, but although I can order them, there are some mismatches with how the Epics are used compared to what Scrum expects, or what Story mapping expects an Epic to be."
"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."
"In Jira, say on the team, no matter the methodology, it doesn't matter what I'm practicing, if I am using the tool for a while and I've compiled some sort of history. If I want to change my workflow, say my team is today using to-do in progress done, and tomorrow, I decide I want to use to-do in review and done, and I apply that new workflow, I have just now effectively lost all of my histories in terms of reporting."
"I would like to have a future-proof idea of the cost and the roadmap for my class."
"Nowadays, many organizations are moving toward the Objectives and Key Results (OKR) framework, and this is something that Jira should be able to accommodate."
"In general, although we use JIRA, we never really learned how to use it properly. The learning curve of the solution is high. It has a lot of power, and yet we don't understand its capabilities."
"While it's very powerful, it's very complex sometimes."
"I want Jira to have more plug-ins, which will allow for more free plug-ins that help with the area of reporting."
"User interface continues to be poor. The product does not have a similar view in the different modules, e.g., staffing vs financial management, it looks like you are working with a different product and it is not easy to use or intuitive."
"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."
"Reporting; need to be able to provide fancy reporting out of PPM, way it is done in OBIEE etc."
"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."
"Portfolio scenarios: This is a very powerful feature. However, it’s limited to analyses."
"There are some limitations when it comes to attaching receipts. For example, if we are going to buy some non-labor-related assets such as hardware, we are not able to attach the receipts in the Financial Management module in version 9.41."
"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."
"Currently, HPE PPM does not allow “Project” approval, but only simple “Demand Request” approval (mobility)."
More OpenText Project and portfolio Management Pricing and Cost Advice →
Jira is ranked 2nd in Application Lifecycle Management (ALM) Suites with 259 reviews while OpenText Project and portfolio Management is ranked 10th in Project Portfolio Management with 24 reviews. Jira is rated 8.2, while OpenText Project and portfolio Management is rated 7.8. 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 OpenText Project and portfolio Management writes "Gives management a cohesive place for tracking business strategies and goals, but cosmetic aspects need work". Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and Polarion ALM, whereas OpenText Project and portfolio Management is most compared with Planview PPM Pro, ServiceNow Strategic Portfolio Management, Smartsheet and Teamwork . See our Jira vs. OpenText Project and portfolio Management 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.
