We performed a comparison between Jira and OpenText ALM / Quality Center based on real PeerSpot user reviews.
Find out in this report how the two Application Lifecycle Management (ALM) Suites solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most valuable features in Jira are the dashboard, reports, and boards that help us to control the advancement of the project."
"The customization and tailoring of the workflows have proven to be very useful."
"The solution helps a lot with scrums."
"It handles all of the issues that we need it to do."
"The most valuable feature is the Burndown Chart to see work that is outstanding."
"Offers a common language set so we can bring people into projects and get them up and running almost immediately."
"The adaptability of the Scrum and Kanban boards for other uses, with careful use of the customization features."
"Offers great multiple reporting charts."
"Micro Focus ALM Quality Center is quite stable."
"Templates: Allows us to standardize fields, workflows throughout hundreds of HPE ALM projects."
"The most valuable Quality Center feature, I find, is the solution's integration with some of our automation tools. For us, the ability to capture and record and the ease of use from a user perspective, are all key."
"The independent view of elevated access is good."
"I love linking/associating the requirements to a test case. That's where I get to know my requirement coverage, which helps a lot at a practical level. So, we use the traceability and visibility features a lot. This helps us to understand if there are any requirements not linked to any test case, thus not getting tested at all. That missing link is always very visible, which helps us to create our requirement traceability matrix and maintain it in a dynamic way. Even with changing requirements, we can keep on changing or updating the tool."
"It's easy to create defects and easy to sync them up with a developer. Immediately, once created, it will trigger an email to the developer and we'll start a conversation with the developer regarding the requirements that have not been matched."
"It provides visibility on release status and readiness."
"Within Quality Center, you have the dashboard where you can monitor your progress over different entities. You can build your own SQL query segments, and all that data is there in the system, then you can make a dashboard report."
"It would be very practical if you can more freely reach the information that is already inside the system. Currently, we have to buy add-ons for it. There is a lot of information in the Jira system that you can handle only through add-ons. You cannot reach such information on your own. If you want to use this information, which is already in the system, you have to buy some add-on to use. For example, information about how much time an assignee is spending on a ticket is there in the system, but you cannot access it without an add-on. JQL is a very good way to reach the data inside Jira. If we can reach more objects, even through JQL, it would be great."
"In Jira, sometimes developers are not getting alerts when Jira is moving out of the SLA to the product development team."
"There should be a way to integrate the mobile application or in some way, make it more clear because at first instance, I didn't understand how to use it."
"Workflows can be improved. We don't use workflows because we can't handle that much complexity. Its interface could be more intuitive for workflows."
"We'd like to see more collaboration tools implemented within the product itself."
"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."
"Its ability to perform true executive-level status reporting could be improved. There are a lot of benefits there, but there are also a lot of things they can and should expand upon."
"I find the dashboard to be Jira's most problematic feature."
"Micro Focus ALM Quality Center could improve its marketing. For example, Tricentis is much better at letting the market know about new solutions and updates. The migration of the tool could improve, but it can be difficult."
"There is room for improvement in the scalability and stability of the solution."
"Only Internet Explorer is supported. That is a big problem. They don't support Chrome and Firefox and so on."
"I'm looking at more towards something more from a DevOps perspective. For example, how to pull the DevOps ecosystem into the Micro Focus ALM."
"The BPT also known as Business Process Testing can sometimes be very time intensive and sometimes might not be very intuitive to someone who is not familiar with BPT."
"Requirements management could be improved as the use is very limited. E.g., they have always stated that, "You can monitor and create requirements," but it has its limitations. That's why companies will choose another requirements management solution and import data from that source system into Quality Center. Micro Focus has also invested in an adapter between Dimensions RM and ALM via Micro Focus Connect. However, I see room for improvements in this rather outdated tool. I feel what Micro Focus did is say, "Our strategy is not to improve these parts within the tool itself, but search for supported integrations within our own tool set." This has not been helpful."
"The solution needs to offer support for Agile. Currently, ALM only supports Waterfall."
"Certain features are lousy. Those features can drag the whole server down. There are times that the complex SQL queries are not easy to do within this solution."
More OpenText ALM / Quality Center Pricing and Cost Advice →
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 266 reviews while OpenText ALM / Quality Center is ranked 5th in Application Lifecycle Management (ALM) Suites with 197 reviews. Jira is rated 8.2, while OpenText ALM / Quality Center 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 OpenText ALM / Quality Center writes "Offers features for higher-end traceability and integration with different tools but lacks in scalability ". Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and Digital.ai Agility, whereas OpenText ALM / Quality Center is most compared with Microsoft Azure DevOps, OpenText ALM Octane, Tricentis qTest, Zephyr Enterprise and OpenText UFT One. See our Jira vs. OpenText ALM / Quality Center report.
See our list of best Application Lifecycle Management (ALM) Suites vendors.
We monitor all Application Lifecycle Management (ALM) Suites 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.
Micro Focus ALM is a complete Test Management tool that can cover Requirements management, Defects management, Test Plan, Test Execution Suites as well as automation test executions with MF UFT (former HP QC). If you have a testing heavy project then MF ALM covers all the testing expectations well.
However, in an integrated environment with development, releases, and testing, JIRA can offer a better experience for JIRA issues (for requirements and incidents/defects), add-on for testing from JIRA marketplace (e.g. X-Ray) and offers a better fitment for DevOps. Developers and testers can work with the same tool for defects. requirements i.e. JIRA and manage testing with JIRA add-ons for Test Management.
I don't know enough about Micro Focus ALM but based from what I have seen it does provide a lot more than JIRA. I have worked with Azure DevOps and know that it can also provide more than JIRA. AZURE DevOps seems to be similar in comparison with Micro Focus ALM. So I would say if it was between JIRA and Micro Focus, then I will choose the latter.