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."I've never had a bug or a bug message that I needed to open a ticket for."
"It is a complete solution. It has more features as compared to other tools, especially the open-source one that we use. It is also easy to administer."
"Integration is good."
"We have not encountered difficulties with the scalability."
"The most valuable feature is the flexibility of the configuration, being able to configure it to suit your own needs."
"It's very flexible. I can define workflows and custom fields and dependencies between issues and projects. And every project can have a custom configuration with my fields, my names for fields, my validations, and my workflows. It's very customizable."
"One of the most valuable features is querying because the jQuery function is very good. Additionally, we can create good designs very easily."
"It is a good defect tracking tool. It has a lot of capabilities and functionalities. There are a lot of graphs and a lot of tracking. It can be sprint-driven if you want."
"The most valuable feature of the solution is taking snapshots while doing the execution of the test cases."
"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."
"The product has all the features that we for application managementat a lower cost."
"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."
"It's also difficult to migrate through, things don't always tie-up. It's not easy to use."
"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."
"There could be an improvement in loading files and images for more than 50 MB. It would be good if it allowed more than 100 MB."
"One major issue that I, and even our business stakeholders, have noticed is related to Epic Link. When Epic Link's background color is a dark color, it effectively becomes unreadable. I wish there was a way for us to change the text color of Epic Link in the Issue Navigator view."
"In JIRA, it's a bit complex in terms of what advanced search queries we use. Sharing them is also a problem. Because TFS is on the cloud, we can easily save that query and share it with our team members."
"My main concern is the administration of projects, especially user groups, and this requires root access rights but there is no concept of layered admin rights."
"ClickUp is a good alternative to Jira, so they have a better interface [GUI]. I don't like Jira's graphical interface - it could be more user-friendly. Jira looks old school."
"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."
"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."
"The pricing should be more competitive."
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.