We performed a comparison between Jira and OpenText AccuRev 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."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 is very user friendly, easy to install, and easy to access."
"The solution is extremely stable."
"The solution works well and does what it needs to do."
"The most valuable feature of this solution is the source linking on the commit level to git."
"The most valuable features in Jira are the dashboard, reports, and boards that help us to control the advancement of the project."
"Jira improved our team collaboration by providing visual visibility and transparency. Everyone could see what tasks were being worked on and the progress made. The development team updated task statuses, making tracking progress and planning sprints easy. If there were any impediments or challenges, we addressed them. This process helped us track our progress."
"The layout, workflow, automation, and metrics are helpful in Jira."
"The most valuable feature of the solution is taking snapshots while doing the execution of the test cases."
"The product has all the features that we for application managementat a lower cost."
"The most valuable feature is the Business Process Testing feature, BPT, because it brings in the most revenue."
"The solution is 100% scalable. It's much more scalable than the customer's capacity for implementing it. We do plan to increase usage ourselves."
"Stability is an area of concern and it needs improvement, otherwise, it's a good product."
"The performance and stability are visibly degrading since the database has been growing every year."
"An area for improvement in Jira is that it's not designed for test management. To use it for test management, you need an add-on or several add-ons, e.g. Xray or Zephyr."
"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."
"The integration could be better in Jira."
"Jira required a significant amount of system resources, particularly for larger organizations with extensive workflows and numerous projects."
"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."
"Jira is raising their prices for the license, which is like a trap because many other providers offer services like Jira but for much cheaper."
"The pricing should be more competitive."
"In the next release, I would like to have a repository for the code which is embedded. Apart from that, it has everything I need."
"It is difficult to gain experience with the product because resources and documentation for learning are not available."
"What I'm missing from the solution is a repository for the code. Something like Git, for example. Some sort of depository for the code that is embedded."
Earn 20 points
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 266 reviews while OpenText AccuRev is ranked 23rd in Application Lifecycle Management (ALM) Suites. Jira is rated 8.2, while OpenText AccuRev is rated 8.6. 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 AccuRev writes "Good packaging features, but reporting is limited". Jira is most compared with Microsoft Azure DevOps, IBM Rational DOORS, OpenText ALM Octane, Rally Software and Polarion ALM, whereas OpenText AccuRev is most compared with Jama Connect. See our Jira vs. OpenText AccuRev 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.