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

"The design of the interface is clean and not too busy visually."
"The ability to design your own workflows is a great feature."
"The board has been a very valuable feature because it can be very simple for teams that are not technical. It can also be highly technical and have lots of data for teams that are technical. So we use it for both instances."
"Jira is quite easy to use and very simple from my point of view."
"The links between tickets are very valuable and the boards I found to be configurable and usable. The boards allow some level of extended configuration and they can be customized according to our project needs. Additionally, it is easy to use."
"Integration is good."
"Jira is flexible and accessible for the end-user. It lets users track their requests. The look and feel are good for our purposes."
"Its integration with Bitbucket, Confluence, and other things is most valuable."
"The most valuable feature is the way the libraries are structured so that they were not folder driven."
 

Cons

"It can have a more high-level view of portfolios. It has quite detailed views, but I would like a high-level view of portfolios. We want to integrate Jira with Microsoft Active Directory, and I don't know how easy or hard it is going to be. I don't know if Jira supports this. We are starting that integration in the last quarter of this year. I hope to find all the required tools for this integration."
"The solution can improve by including test management functionality in a native bundle without plugins."
"I would love to have more features to make nice documents, like Release Notes or a feature overview, right from JIRA."
"It would be ideal if the solution could be available as a mobile application."
"The filtration could be better."
"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."
"The features are not intuitive. It would be good if there were templates."
"The sprint-related graphics need to be improved."
"It doesn't allow you to connect to multiple different tracking tools."
 

Pricing and Cost Advice

"There is a need to make yearly payments towards the licensing costs attached to the solution. The product offers flexibility in pricing since it depends on the memory bits you have used."
"It is subscription-based, and we probably pay yearly. I would rate it a four out of five in terms of price."
"We used to be on a perpetual license provided by our clients."
"It does not cost that much."
"Its price is fine, but we would like it to be less expensive. We are paying on a yearly basis."
"The price of the solution could be lower."
"For very small companies, if you have less than 10 individuals, it is $10 a year for each of the products. When we were a part of the enterprise and had more than 10 people using it, or before they came up with this solution for small companies, it was $2,500 a year for the license for Jira and Confluence, and I believe something like $600 a year to perpetuate the license. I can't remember if it was $600 or $2,500 annually. It was for up to 25 people at the time, and this was in the early 2000s and mid 2000s."
"The ballpark figure is about $100 a month."
"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.
845,040 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
53%
Manufacturing Company
8%
Financial Services Firm
6%
Computer Software Company
5%
Computer Software Company
21%
Financial Services Firm
19%
Healthcare Company
8%
Retailer
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: March 2025.
845,040 professionals have used our research since 2012.