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 adaptability of the Scrum and Kanban boards for other uses, with careful use of the customization features."
"It benefits us because we have globally located teams. Our team members work in different geographies, so the product is a better way to manage progress and see the status of different tasks"
"The agile framework works well, and I pretty much live by that. Everything, such as sprint management, is laid out."
"It also works well with all the integrated tools that you buy."
"We integrate Jira with QRadar which is helpful."
"The burndown chart is also helpful when it comes to reporting and allows us to know where we are going, especially during development."
"Jira is great for story management."
"The burndown charts help track 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."
"Cross project customization through template really helps to maintain standards with respect to fields, workflows throughout the available projects."
"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."
"I personally found the defect tracking feature very useful in my ongoing project."
"Templates: Allows us to standardize fields, workflows throughout hundreds of HPE ALM projects."
"By using QC we broke down silos (of teams), improved the organization of our tests, have a much better view of the testing status, and became much quicker in providing test results with document generation."
"It has a brand new look and feel. It comes with a new dashboard that looks nice, and you can see exactly what you have been working with."
"The test-case repository and linkage through to regression requirements will absolutely be a key component for us. We haven't got it yet, but when we've got an enterprise regression suite, that will be a key deliverable for them. We will be able to have all of the regression suite in one place, linked to the right requirements."
"They can maybe dumb down the directions for building the automation a little bit because to be able to build out the automation, I had to play around with it and learn what all the fields meant and what they were referencing. I don't have an IT background originally. My background is in biology, and I got into project management by chance. I am good at it, but I haven't really worked with coding languages. In terms of writing automation, it is easier for devs because they intuitively know what they're being asked, but as a PM who originally didn't have IT experience, it was a little bit daunting at first. It could also have an extra hierarchy to be able to allow tasks under stories. It could be the way it is set up at our organization, but currently, under stories, you can have sub-tasks, but you can't create a task. Being able to customize your hierarchy a little bit more would be beneficial because sometimes, the devs would say, "Well, here's a story, and now we need sub-tasks," but as we were building out the sub-tasks, sometimes we had to go a step lower to dig in a little bit more, and we couldn't do that."
"I have had problems with performance and unresponsiveness. All of a sudden, the performance slowed down, and I had a number of users that could not use the tool."
"This solution would be improved with the inclusion of integration with SVN, and auto-sync with the build release number."
"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."
"It would be ideal if Jira had future functionalities to integrate more easily with various aspects of code reviews."
"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 also wish Jira had an indicator to tell you that you are approaching the limit for the story points that can be delivered during a sprint. I don't think there is an indicator like that, but such an indicator will be very helpful because then I will be easily able to see that we are approaching the limit."
"For our company, we're thinking about not only project management solutions but also collaboration solutions, and maybe if Jira had a chart or quick commenting option, it would be great."
"There is room for improvement in the scalability and stability of the solution."
"Browser support needs improvement. Currently, it can only run on IE, Internet Explorer. It doesn't work on Firefox, doesn't work on Chrome, doesn't work on a Mac book. Those are the new technologies where most companies move towards. That's been outstanding for quite a while before it even became Micro Focus tools when it was still HP. Even before HP, that's always been an issue."
"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."
"The downside is that the Quality Center's only been available on Windows for years, but not on Mac."
"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."
"The integration could be improved because with Agile technology you are working more quickly than with a top-down methodology."
"The product is good, it's great, but when compared to other products with the latest methodologies, or when rating it as a software development tool, then I'll have to rate it with a lower score because there's a lot of other great tools where you can interconnect them, use them, scale them, and leverage. It all depends on the cost."
"Cross project reporting is limited to similar database schemas"
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 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.