Try our new research platform with insights from 80,000+ expert users

Jira vs PractiTest comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 15, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Jira
Ranking in Application Lifecycle Management (ALM) Suites
1st
Average Rating
8.2
Reviews Sentiment
6.9
Number of Reviews
274
Ranking in other categories
Application Requirements Management (2nd), Project Management Software (2nd)
PractiTest
Ranking in Application Lifecycle Management (ALM) Suites
21st
Average Rating
8.8
Reviews Sentiment
6.9
Number of Reviews
7
Ranking in other categories
Test Management Tools (18th)
 

Mindshare comparison

As of April 2025, in the Application Lifecycle Management (ALM) Suites category, the mindshare of Jira is 21.9%, down from 23.9% compared to the previous year. The mindshare of PractiTest is 0.4%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Lifecycle Management (ALM) Suites
 

Featured Reviews

Saroj Ekka - PeerSpot reviewer
Offers good repository integration, sprint board and easy to set up
There are some features and reports we need that are not there. For example, if I have to find out the capacity of the current sprint by user and compare it with the previous sprint, that visibility isn't there. We can know the capacity and what happened with the whole sprint, but not for an individual person to see where it's falling and how it's tracking. Report and analytics capabilities are important for a product manager. That visibility is important, so we use Jira. Some of the features are there, and I use my own Excels or other data things to compensate for that.
DC
Flexible and intuitive with easy reporting, and good support that is instantly available through chat
It doesn't allow you to connect to multiple different bug tracking tools at the same time. This is not an issue if you only have one bug tracker but we can potentially use different tools for different projects. As an example, if you connect PractiTest to Jira for one project, that's the one you have to use for all projects. We had a requirement to connect with Jira for one project, and a different tool for another, project but it was unable to accommodate that unfortunately. I would therefore like to see it easier to integrate with bug tracking tools at project level which would give each project the opportunity to use a different bug tracker if required.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"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."
"It helps me to use virtual Scrum boards across four locations, three time zones, and to plan my work. It fully supports the Scrum approach, and the Agile way of working, and it has Agile thinking behind it.."
"You no longer need to email people. You can mention them right in Jira and have conversations there."
"The most valuable features of this solution are workflow and reporting."
"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."
"Integration is good."
"Has a good dashboard with good tracking features."
"The flexibility to create different flows is most valuable."
"The most valuable feature is the way the libraries are structured so that they were not folder driven."
 

Cons

"Whenever you edit a story, whatever you have changed takes a bit of time to save."
"It would be very useful to have drag and drop time tracking."
"Scripts should be more readily available for implementing projects."
"Could be more stable with more integrations."
"The performance is not so good sometimes. I know that fully depends on the implementation and the IT environment of Jira or the version of Jira installed. The performance is sometimes not so good. I would like to have a better response time from the Jira server. And it fully depends on the administration side of the Jira."
"This solution could be improved by including a different model for the overall planning perspective. There's a Jira portfolio that we aren't using. The only challenge we're facing is that we cannot see the overall planning."
"There needs to be an easier way to capture a few metrics. I wish there was an easy way for Jira to explain to me what has been added after the sprint has been done. Currently, it is a bit difficult for me to tell. In addition, when rolling over stories from one sprint to another, it is kind of difficult for me to find out how many story points were actually rolled over without going into Jira and doing an analysis. I wish Jira would somehow aggregate that information for me so I can easily report about it."
"Sometimes, we create the same bug with two or three different Jira tickets in my company, which leads to duplication, making it an area where improvements are required."
"It doesn't allow you to connect to multiple different tracking tools."
 

Pricing and Cost Advice

"The tool's pricing is expensive. The new pricing is indeed quite expensive compared to what it was a few years ago. Last year, when we intended to renew our subscription, we found the pricing considerably higher."
"Compared to the value Jira provides, it’s not that expensive. It has an yearly licensing cost."
"The price of the solution could be less expensive. We pay annually for the solution."
"It depends on the type of license. In terms of subscription, it is cheap, and it works pretty well."
"We are on an annual license to use Jira."
"There are no additional costs to the standard licensing."
"The tool is expensive."
"If I compare Jira's licensing model with that of other products, I think that the other products have a much better licensing model."
"Pricing is probably in the middle, it's not the cheapest but it's not the most expensive."
report
Use our free recommendation engine to learn which Application Lifecycle Management (ALM) Suites solutions are best for your needs.
848,716 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
50%
Manufacturing Company
8%
Financial Services Firm
7%
Computer Software Company
6%
Computer Software Company
23%
Financial Services Firm
20%
Government
6%
Healthcare Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

Questions from the Community

Is Jira better or would you go with Micro Focus ALM Octane?
Hi Netanya, Basically , it all depends on the use cases for your environment and the business needs. Hope the below data may be relevant to you for identifying your needs and deciding on the approp...
Which is better - Jira or Microsoft Azure DevOps?
Jira is a great centralized tool for just about everything, from local team management to keeping track of products and work logs. It is easy to implement and navigate, and it is stable and scalabl...
What is your experience regarding pricing and costs for Jira?
We operate under a nonlimited license with Jira, allowing a number of users to access it with a single enterprise license.
Ask a question
Earn 20 points
 

Comparisons

 

Also Known As

Jira Software
No data available
 

Overview

 

Sample Customers

Square, Nasa, eBay, Cisco, SalesForce, Adobe, BNP Paribas, BMW and LinkedIn, Pfizer, Citi.
Canonical, SAS, Amobee, Play Buzz, Abbott, Aternity, Zerto, Freeman
Find out what your peers are saying about Jira vs. PractiTest and other solutions. Updated: April 2025.
848,716 professionals have used our research since 2012.