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."We use it for capacity planning. We need to gauge and assess whatever is coming to our pipeline and then everything comes to the pipeline, appears as a pic, and then based on that, we create the story points and we take it from there."
"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."
"It includes by default all the necessary tools for a project manager to work and make their work more efficient."
"The most valuable features are the customized Dashboard, Sprint Planning, and Automatic Notifications."
"When we run the Jenkins pipeline, the build is already automatically connected to Jira. We've been able to integrate the ecosystem we created using this automation tool."
"JIRA stores history of changes, which helps a lot to track who, when, and why the issue was modified."
"Jira's collaborative features, such as comments, notifications, and real-time updates, facilitate better communication."
"The agile framework works well, and I pretty much live by that. Everything, such as sprint management, is laid out."
"The solution is very user-friendly."
"You can do your development from start to finish: starting with the requirements, ending with defects, and testing in-between."
"ALM Quality Center is a reliable, consolidated product."
"The independent view of elevated access is good."
"So the first impression that hits me about HP UFT 14.0 (formerly QTP) is that it seems to be a whole lot faster! But that could be subjective, as I'm running it on a high end gaming system."
"Defect management is very good."
"It's basically the way to show the work that we do as QA testers, and to have a historical view of those executions."
"You can maintain your test cases and requirements. You can also log the defects in it and make the traceability metrics out of it. There are all sorts of things you can do in this. It is not that complex to use. In terms of user experience, it is very simple to adopt. It is a good product."
"The reporting needs to be better."
"Grid: It is really strange that there is no possibility to edit an item in the grid. You need to go inside, and even then, not all items are editable, so you need to switch to edit mode. That's too many clicks and switches."
"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."
"I would like to see more integration available with more tools."
"I have to go through a lot of processes to consider it done. I have to log in then change the logins and make it interesting. It's not so good for testing."
"We'd like to see Jira have more integration with a development ID."
"The plugin management needs a lot of work."
"There is a difficulty viewing all the attachments because they are shown in one place. I would like attachments to be shown at the comment level."
"We are looking for more automation capabilities."
"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."
"The Agile methodology is now being used across all the organizations, but in this solution, we don't have a dashboard like Jira. In Jira, you can move your product backlogs from one space to another and see the progress, that is, whether a backlog is in the development stage or testing stage. Micro Focus ALM Quality Center does not have this feature. It is typically very straightforward. You just execute the test cases from it, and you just make them pass, fail, or whatever. They can also improve its integration with Jira. The browser support needs to be improved in this because it supports only Internet Explorer as of now. It does not have support for Firefox, Chrome, Safari, or any other browser. There are also some performance issues in it. Let's say that you are doing the testing, and you found something and are logging the defect. When you try to attach several or multiple screenshots with the defect, it slows down, which is a very common problem people face. I would like them to include a functionality where I am able to see the reports across all the projects. When you have multiple projects, being a manager, I would like to see the reports across all the projects. Currently, there is no single sign-on through which we can get all the information at one place. You need to log into it project-wise. If you have ten projects, you can't view the information in one dashboard."
"We operate in Sweden, and there are not so many Swedish people that know the product."
"We would like to have support for agile development."
"Quality Center's UI is outdated, and it's a little bit slow on the login part and different parts of the application. That's why we're switching solutions. I believe most companies are switching to Octane or something else. Micro Focus should enhance the interface and reports."
"The solution needs to offer support for Agile. Currently, ALM only supports Waterfall."
"The uploading of test scripts can get a little cumbersome and that is a very sensitive task. They could improve on that a lot. It's really important that this gets better as I'm loading close to a thousand test scripts per cycle."
More OpenText ALM / Quality Center Pricing and Cost Advice →
Jira is ranked 2nd in Application Lifecycle Management (ALM) Suites with 17 reviews while OpenText ALM / Quality Center is ranked 6th in Application Lifecycle Management (ALM) Suites with 17 reviews. Jira is rated 8.0, while OpenText ALM / Quality Center is rated 8.0. The top reviewer of Jira writes "Stable with good documentation and needs very little maintenance". On the other hand, the top reviewer of OpenText ALM / Quality Center writes "It is a stable solution, and customer service is its most valuable feature". Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Polarion ALM and Digital.ai Agility, whereas OpenText ALM / Quality Center is most compared with Microsoft Azure DevOps, OpenText ALM Octane, Tricentis qTest, Zephyr Enterprise and Tricentis Tosca. 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.