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 way it interfaces with Bitbucket and other things like that is valuable. Reporting and being able to link various issues or stories together are also valuable. We call them stories, and they're general reports."
"The roadmap feature and the ability to integrate with Power BI are probably the most valuable features in it. It is a great solution. I absolutely love it. It is a tool that was designed for project management, and it has been awesome to work with it so far. I also love Confluence."
"In terms of scrum teams, I find that usually, the product backlog depends on charts and especially reports like Sprint Reports. I find the reports to be very useful."
"The agile framework works well, and I pretty much live by that. Everything, such as sprint management, is laid out."
"We have around 2000 plus users, so scale wise, there are no issues. We can easily scale up with multiple users."
"No other platform can compete on speed or search."
"The timeline management is great."
"The workflows are very easy to handle as far as scalability goes."
"The most valuable feature is the way the libraries are structured so that they were not folder driven."
 

Cons

"The reporting tool and the approval tool need work."
"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."
"To improve Jira, providing proper documentation, examples, or snippets for scripting workflows would be beneficial."
"From the project management perspective, I would say there are a lot of different issues that could be tweaked. There can be small improvements with traceability, for example."
"The Jira dashboards could be more useful. The dashboards have good widgets but the comparison of data over time or extraction of trends from the data is not easy."
"The reporting needs to be better."
"it would be helpful to have a better tutorial for learning and to have a better understanding of what the features are and what they do."
"It lacks features to cover all testing aspects, so we often integrate it with other plugins or tools like X-ray."
"It doesn't allow you to connect to multiple different tracking tools."
 

Pricing and Cost Advice

"The price at the moment for Jira is okay. I'm absolutely not amused with the plans to try to drive us to the cloud or to other licensing models. For the very simple reason that we are a company in the defense sector where cloud is problematic in a number of the domains. We are now approximately 60 users and the new policy will actually confront us with an upscale to approximately 500 users. I find it unacceptable, and may potentially lead us to look for another solution."
"It is an affordable tool."
"I don't have the number, but I sure wish Jira was less expensive. Its price point should be a little lower, and it should be more flexible for users who are just ticket viewers."
"If you are using just Jira, it is cheap, but if you start to use it and you feel you need some more services or more functions, then you have to buy add-ons, which can make it expensive."
"The price of Jira is reasonable."
"Our client handles the licensing aspect. They have not yet purchased the premium version."
"To try this solution, use their cloud offering to get familiar. After that, it's in my view worth the money."
"When you get larger, the pricing becomes very, very steep."
"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.
849,190 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Educational Organization
51%
Manufacturing Company
8%
Financial Services Firm
7%
Computer Software Company
5%
Computer Software Company
22%
Financial Services Firm
20%
Manufacturing Company
6%
Government
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.
849,190 professionals have used our research since 2012.