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."It's easy to deploy."
"One of the most valuable features is querying because the jQuery function is very good. Additionally, we can create good designs very easily."
"Its visual display and ease of use are most valuable."
"We can create multiple boards for the same product backlogs."
"We've found the scalability to be good."
"You can record your unit testing, regression testing, UATs, et cetera."
"It includes by default all the necessary tools for a project manager to work and make their work more efficient."
"I liked the flexibility of the application. It was pretty user-friendly."
"It allows us to easily make linkage and dependencies, with plenty of integrations."
"The enhanced dashboards capabilities are useful for senior management to view the progress of releases under the portfolio in one go and also drill down to the graphs."
"Quality management, project management from a QA perspective - testing, defect management, how testing relates back to requirements."
"I personally found the defect tracking feature very useful in my ongoing project."
"We are able to use Micro Focus ALM Quality Center for test management, defect management, test process, test governance activities, and requirement management. We are able to achieve all of this, the solution is very useful."
"The most valuable user feature that we use right now is the camera."
"This solution is open and very easy to integrate. The interface is good too."
"Being able to manage tests as this is something very difficult to find in other products."
"Users can be confused about how to use this tool as it's very complex."
"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."
"I do know the initial setup was pretty complicated. The user interface could be better organized and easier. "
"It would be ideal if Jira had future functionalities to integrate more easily with various aspects of code reviews."
"Once the solution is deployed, it's not easy to configure."
"Ease of administration and customization. It is really clunky in this area."
"Atlassian has multiple tools and it becomes difficult for a customer to process everything differently. Atlassian should combine them and form a single solution for DevOps by including the Jira Confluence, Bitbucket, Bamboo, and others. This would be much easier for customers by purchasing a package, rather than purchasing bits and pieces. With Azure DevOps and other companies, it becomes easier to go with one company having multiple areas that they can cater to, but in Atlassian, the problem is that you have to select different solutions to have a full package. For example, to have document management customers have to purchase Confluence and for Git repository management they have to purchase Bitbucket, et cetera. There is always another add-on that you need to attach to have a complete solution in Jira."
"The reporting part is a little bit difficult for me. It is not so easy. There should be a simpler way to track the efforts of our team. For example, in an Excel sheet, there is a feature for filtering. It would be much better if we can use something like that. Currently, for a complex query, we need to use Jira Query Language. Using Jira Query Language every time is not efficient for me."
"Currently, what's missing in the solution is the ability for users to see the ongoing scenarios and the status of those scenarios versus the requirements. As for the management tools, they also need to be improved so users can have a better idea of what's going on in just one look, so they can manage testing activities better."
"An area for improvement in Micro Focus ALM Quality Center is not being able to update the Excel sheet where I wrote the test cases. Whenever I update some test cases, I'm unsuccessful because there is overlapping data or missing cases from the sheet."
"Cross project reporting is limited to similar database schemas"
"HP-QC does not support Agile. It is designed for Waterfall. This is the number one issue that we're facing right now, which is why we want to look for another tool. We're a pharmaceutical services company, so we require electronic signatures in a tool, but this functionality isn't available in HP-QC. We don't have 21 CFR, Part 11, electronic signatures, and we need compliant electronic signatures. Some of the ALM tools can toggle between tabular format and document format for requirements, but the same feature is not available in this solution. There is also no concept of base-lining or versioning. It doesn't exist."
"I would rate it a 10 if it had the template functionality on the web side, had better interfaces between other applications, so that we didn't have dual data entry or have to set up our own migrations."
"It can be quite clunky, and it can easily be configured badly, which I've seen in a couple of places. If it is configured badly, it can be very hard to use. It is not so easy to integrate with other products. I've not used Micro Focus in a proper CI/CD pipeline, and I haven't managed to get that working because that has not been my focus. So, I find it hard. I've often lost the information because it had committed badly. It doesn't commit very well sometimes, but that might have to do with the sites that I was working at and the way they had configured it."
"As soon as it's available on-premises we want to move to ALM Octane as it's mainly web based, has the capability to work with major tests, and integrates with Jenkins for continuous integration."
"When it came to JIRA and Agile adoption, that was not really easy to do with ALM. I tried, but I was not able to do much on that... There is room for improvement in the way it connects to and handles Agile projects."
More OpenText ALM / Quality Center Pricing and Cost Advice →
Jira is ranked 2nd in Application Lifecycle Management (ALM) Suites with 259 reviews while OpenText ALM / Quality Center is ranked 6th 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.