We use Jira for project management and tracking.
Head Section Mobile Developer at a manufacturing company with 10,001+ employees
Useful in project management and tracking but improvement is needed in integration
Pros and Cons
- "We use Jira for project management and tracking."
- "I want the tool to integrate connectors."
What is our primary use case?
What needs improvement?
I want the tool to integrate connectors.
For how long have I used the solution?
I have been using the product for five years.
What do I think about the stability of the solution?
Jira is stable.
Buyer's Guide
Jira
March 2025

Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
844,944 professionals have used our research since 2012.
What do I think about the scalability of the solution?
The solution is scalable. My company has 300 users.
How was the initial setup?
Jira's deployment is easy.
What's my experience with pricing, setup cost, and licensing?
The tool's pricing is reasonable.
What other advice do I have?
I rate the product a nine out of ten overall.
Disclosure: I am a real user, and this review is based on my own experience and opinions.

Tech Lead DevOps (Manager) at Logiq Worlds
Beneficial integration, simple implementation, and scalable
Pros and Cons
- "The most valuable feature of Jira is the integration with all the different Atlassian tools. They all integrate very easily."
- "Atlassian has multiple tools and it becomes difficult for a customer to process everything differently. Atlassian should combine them and form a single solution for DevOps by including the Jira Confluence, Bitbucket, Bamboo, and others. This would be much easier for customers by purchasing a package, rather than purchasing bits and pieces. With Azure DevOps and other companies, it becomes easier to go with one company having multiple areas that they can cater to, but in Atlassian, the problem is that you have to select different solutions to have a full package. For example, to have document management customers have to purchase Confluence and for Git repository management they have to purchase Bitbucket, et cetera. There is always another add-on that you need to attach to have a complete solution in Jira."
What is our primary use case?
We are using Jira for the internal project and issue management or tracking.
What is most valuable?
The most valuable feature of Jira is the integration with all the different Atlassian tools. They all integrate very easily.
What needs improvement?
Atlassian has multiple tools and it becomes difficult for a customer to process everything differently. Atlassian should combine them and form a single solution for DevOps by including the Jira Confluence, Bitbucket, Bamboo, and others. This would be much easier for customers by purchasing a package, rather than purchasing bits and pieces. With Azure DevOps and other companies, it becomes easier to go with one company having multiple areas that they can cater to, but in Atlassian, the problem is that you have to select different solutions to have a full package. For example, to have document management customers have to purchase Confluence and for Git repository management they have to purchase Bitbucket, et cetera. There is always another add-on that you need to attach to have a complete solution in Jira.
For how long have I used the solution?
I have been using Jira for more than five years.
What do I think about the stability of the solution?
I have found Jira to be stable.
What do I think about the scalability of the solution?
Jira is a scalable solution.
How are customer service and support?
I did not have any issue with the use of technical support from Jira.
How was the initial setup?
The initial setup was easy.
What other advice do I have?
I would advise others that Jira is a good solution and I would recommend it.
I rate Jira a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Jira
March 2025

Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
844,944 professionals have used our research since 2012.
Director at a financial services firm with 10,001+ employees
Keeps things organized and keeps track of time
Pros and Cons
- "A stable solution with no unplanned downtime."
- "Integrates with other components."
- "Slow when integrating with other components."
What is our primary use case?
I use Jira for the development of different versions of software, upgrading it from one version to another, and developing and collecting specs for the new versions.
What is most valuable?
I like that Jira keeps track of time and is good for how it organizes.
What needs improvement?
Jira has a lack of graphical interface that maps the different cases to the space or in the project. For example, if you have a project that has a big diagram of component systems, people, and use cases, each of those Jira cases usually can be mapped to a specific location. This can be enhanced by a curve set of Jira, or a curve set of screens, where you can map on which pieces of the project you were working on at that particular screen. When working on the left side of the diagram, or the right side of the diagram, you should be able to request all those Jira that are related to that part of the project.
If a system has ten different steps of data flow and the components are clear. You should be able to map those Jira cases to different steps in the process. This would show you how a field or component is related to a location in the diagram. The diagram then would show all the cases waiting to be done or already done.
Jira works too slow, especially when you are in a big organization with thousands of users. It is also too slow when integrating with other components like SVN or with a built system. I would like to see everything that Jira does is under have a second response time.
For how long have I used the solution?
I have been using Jira for about one year.
What do I think about the stability of the solution?
Jira is a stable solution, other than planned downtime, it has no downtime.
What do I think about the scalability of the solution?
Jira is integrated with other components in our system, like the build and release systems.
How are customer service and support?
We use internal technical support.
What other advice do I have?
I would recommend that an organization implementing Jira ensure that someone gets training both at the developer level and the project manager level. The developer needs to know what needs to be done, what are the components and why are they there. The project manager should join the training and determine if there is a relation between multiple projects to see that they are really integrated well into other components of continuous integration and continuous delivery.
Because of the slowness, I would rate Jira an eight out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Software Engineer at a financial services firm with 10,001+ employees
Provides high visibility into the development pipeline
Pros and Cons
- "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."
- "I'd like to see better notetaking capabilities so every user can get notes when someone provides comments on a Jira ticket. So if they don't want to provide the comments on the Jira ticket, they can get the personal notes in a Jira tool for every profile."
What is our primary use case?
Currently, we're using it as a tracking tool. It helps our development department operate more efficiently while enabling the business side of the company to understand and track things better. For example, if we get a requirement from the business side, they don't tell us the status of the current cover every time. So basically what we do, if we complete development or make it to the development phase, then we can change the status in Jira. If the other departments want to see the progress, they can go to the Jira dashboard. So this reduces the amount of necessary communication between the business side and developers. Developers can mainly focus on the development instead of having to answer questions from other departments.
What is most valuable?
When we get a sign-off for a management request, we must catch it in our email inbox. Now we can get the sign-off through Jira, and I've automated this. For example, we can get the Jenkins pipeline results for every build we create and have that result plugged into Jira. So 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. If you open Jira, you get the development tab there, so you can find out everything a company made under this Jira or what brand is created under this Jira. As a developer, I find this feature valuable.
What needs improvement?
Jira could be simplified and integrated more with standard corporate communications tools. Say, for example, we have one indication of Jira in Confluence. So if we type a Jira ID into Confluence, it gives us all the information about the Jira profile. I would like to see this feature integrated with email platforms so we can just put our Jira ID or Jira link into an email and get all the details automatically. This kind of integration and automation would be helpful.
I'd like to see better note-taking capabilities so every user can get notes when someone provides comments on a Jira ticket. So if they don't want to provide the comments on the Jira ticket, they can get the personal notes in a Jira tool for every profile. It's not something for the business side, but developers can track what work is finished and what still needs to be done. Jira could integrate better with Jenkins, which isn't fully supported on the Jira dashboard yet. I think it would be good to monitor the build's progress directly. That way, we don't have to attach it. We can do it from the background. Some workflow customization would also be good.
For how long have I used the solution?
In the initial phase, I was using Jira for development and testing purposes. A story was assigned to me, and I just changed the standards and everything. But in the past six months, I have worked with configurations, adding different workflows, and all the other features.
What do I think about the stability of the solution?
Jira is pretty stable most of the time. However, we have an intranet on our side, and sometimes there are too many users. My company currently has four different departments at the top level. Each of the four departments has fewer than nine Jira users. My current department has approximately seven or eight users. So there are times when Jira goes down, and we find it difficult to log in. But we are trying to increase the capability of servers. Other than that, it's working fine.
What do I think about the scalability of the solution?
We have migrated to GCP, and we're using the internal cloud servers, so we can easily integrate Jira into a server if we want. Scalability is a matter of cost. We just need to present our management with a valid reason for increasing capacity, and if they approve, it's an easy process for us.
How are customer service and support?
We had to call Jira support for help with integration. For example, when I was trying to integrate Jira with my GitHub bot, I had to provide a specific kind of access and then run some scripts to find out if I had enough available space. After that, it's a smooth process.
How was the initial setup?
The Jira setup is a bit complicated because we're deploying it in our internal servers. So we have to manage a lot of things ourselves. For example, when the new version of Jira comes in, we have to patch our servers and update our certificates. And then, for deployment, we have pipelines that we need to trigger. That's not too hard, but the patching and upgrading can be complex.
If it's a smooth deployment, it just takes 30 minutes because we only have to replicate it on a different server. So currently, we have more than 20 servers. So every time we deploy, we create a replica on every server, which takes time because we have to verify that it's working. In total, it's about two hours of downtime in Jira, so we do this at night.
Currently, more than 10 people are involved with maintenance. For my team, I do the deployment and configurations. But if there is some fundamental change or a serious bug, a separate team handles this.
What's my experience with pricing, setup cost, and licensing?
I don't deal with the money side of things. I just specify the requirements and the company handles everything. We are using it for many tasks so it seems like the price is reasonable.
What other advice do I have?
I rate JIRA eight out of 10. I think it's a great tool. I have been working with this tool for the past two years and I use it every day.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Google
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Information Technology Program Manager at a wholesaler/distributor with 10,001+ employees
Very stable with valuable Kanban boards, but needs better reporting capabilities for customized reports
Pros and Cons
- "Kanban boards are most valuable"
- "The reporting capabilities, specifically customized reports, should be improved. The out-of-box reports don't meet our needs. We are big into customizing our reports, and being able to do ad hoc reporting would be good."
What is our primary use case?
We are using it for bug tracking and new feature development. We have its latest version.
How has it helped my organization?
Using Kanban boards has allowed us to become a flow-based organization versus a sprint-based organization.
What is most valuable?
Kanban boards are most valuable.
What needs improvement?
The reporting capabilities, specifically customized reports, should be improved. The out-of-box reports don't meet our needs. We are big into customizing our reports, and being able to do ad hoc reporting would be good.
For how long have I used the solution?
I have been using Jira for about three and a half years.
What do I think about the stability of the solution?
It has been very stable.
What do I think about the scalability of the solution?
I believe it has been scaling. I don't really work with that group, and I am not sure. We've got at least a thousand people on it, and to my knowledge, it has been fine at least for our needs. It is being used extensively in our company. We don't have any plans to increase its usage.
How are customer service and technical support?
I have not had any interface with their technical support.
Which solution did I use previously and why did I switch?
I have used Microsoft Team Foundation Server in the past. I switched to Jira because of the job change. Microsoft Team Foundation Server had a number of features that I don't see in Jira. It had good visual charting.
How was the initial setup?
I wasn't a part of that group.
What other advice do I have?
There are some good and valuable tool plugins that make it a much better tool. I've got plugins that cover most of the features that were lacking. There are some specific plugins that are targeted for specific kinds of use cases.
I would rate Jira a seven out of ten. It all comes down to reporting. It should have better and more robust reporting.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Director at a computer software company with 10,001+ employees
Defines how we track time and permissions; we can create multiple boards
Pros and Cons
- "We can create multiple boards for the same product backlogs."
- "Not very intuitive for project admins."
What is our primary use case?
My people use ASS. I can define spins, I can define roadmaps, I can define components, I can do releases, I can define all kinds of issue types, heartbeats, some of those things. I'm using it for both business and software. In software we have Scrum and Kanban onboard, whereas for business we have the service and then there are those other options. We have multiple use cases. I'm the director of the company.
What is most valuable?
I like almost everything about Jira. It defines how we track time and the way we define permissions. We can create multiple boards for the same product backlogs.
What needs improvement?
I think that for users the solution is very intuitive but for project administrators, the way the product is defined is not very intuitive. There are too many ways to do the same thing. The setup of Jira sometimes becomes very, very cumbersome and difficult. It's not very easy for people on the project admins to really understand how to set up the product because of these features. If they were better organized and the documentation improved so that people would actually be able to figure out how to use Jira, that would be helpful. There are not many videos and it can be very challenging for anybody not familiar with the product. There are 50 users on the project I'm working on.
For how long have I used the solution?
I've been using this solution on and off for the last eight years.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
The solution is scalable.
How are customer service and technical support?
We haven't really used technical support.
How was the initial setup?
The initial setup takes a bit of time because it has so many features that you should be aware of, but of course it provides a lot of out of the box features that you can use right away. You can set up in 10 minutes or 10 days, it's very rich. I was able to do the deployment myself with some extra help.
What's my experience with pricing, setup cost, and licensing?
For up to 10 users, the solution is free but above that there are licensing costs.
What other advice do I have?
I would rate this solution an eight out of 10.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
System Engineer at a consultancy with 10,001+ employees
Effective defect management, saves time, and has substantial analytics
Pros and Cons
- "Jira provides substantial analytical aspects, especially in defect categorization and routing."
- "From an automation perspective, there are more aspects that could be needed, especially regarding natural language reporting in the generative AI context."
What is our primary use case?
I have used Jira for defect management and issue management. This includes defect categorization, defect analysis, and defect summary, as well as exporting the defects. I have primarily used it from a user side perspective in both ITSM and agile delivery contexts.
How has it helped my organization?
Jira provides substantial analytical aspects, especially in defect categorization and routing. These features contribute to significant effort savings, roughly between ten to 15 person-days. Additionally, it aids in program management and overall effort management.
What is most valuable?
Jira provides substantial analytical aspects, especially in defect categorization and routing. These features contribute to significant effort savings, roughly between ten to fifteen person-days. Additionally, it aids in program management and overall effort management.
What needs improvement?
From an automation perspective, there are more aspects that could be needed, especially regarding natural language reporting in the generative AI context. I did an integration with UiPath on Jira, focusing on defect routing, however, the API documentation was not adequate.
For how long have I used the solution?
I have used Jira for almost eight to ten years.
What other advice do I have?
Jira is definitely recommended. I'd rate the solution eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Last updated: Nov 26, 2024
Flag as inappropriateAws Devops Engineer at Borgward Technology India Private Limited
Easy to use, performs well, and has a simple user-interface
Pros and Cons
- "The user interface is simple."
- "The stability could be improved."
What is our primary use case?
I use the tool to review code quality and communicate with the QA team. I also use the product to raise tickets with my senior management for issues I cannot resolve.
What is most valuable?
The user interface is simple. It performs well. It is easy to use. Anyone can use the product.
What needs improvement?
The stability could be improved.
For how long have I used the solution?
I have been using the solution for one year and two months.
What do I think about the stability of the solution?
I haven’t had any issues with the stability of the tool. I rate the stability eight out of ten.
How was the initial setup?
The initial setup is simple. We have completely migrated to the AWS cloud.
What other advice do I have?
I will recommend the tool to others. Overall, I rate the solution an eight out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.

Buyer's Guide
Download our free Jira Report and get advice and tips from experienced pros
sharing their opinions.
Updated: March 2025
Product Categories
Application Lifecycle Management (ALM) Suites Application Requirements Management Project Management SoftwarePopular Comparisons
Microsoft Azure DevOps
OpenText ALM / Quality Center
TFS
Polarion ALM
Rally Software
OpenText ALM Octane
Codebeamer
Jama Connect
Jira Align
PTC Integrity
IBM Engineering Lifecycle Management (ELM)
Helix ALM
Digital.ai Agility
Planview AgilePlace
Atlassian ALM
Buyer's Guide
Download our free Jira Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Has anyone tried integrating HP ALM and JIRA ?
- Can JIRA provide integration to SAP automation?
- What Is The Biggest Difference Between JIRA And Microsoft Azure DevOps?
- What Is The Biggest Difference Between AgileCraft And JIRA?
- What is the biggest difference between JIRA and Micro Focus ALM?
- Which is better - Jira or Microsoft Azure DevOps?
- Is Jira better or would you go with Micro Focus ALM Octane?
- Is Jira a suitable solution for both agile and waterfall projects?
- Which tool is integrated better with Jira - Micro Focus ALM Quality Center or TestRail by Gurock?
- What are the equivalent Microsoft tools to Atlassian Confluence and Jira?