We use Jira as a communication tool for tasks and epics. Everything is in one place in the ticket, and it's helpful to communicate with the team. We don't have to use Slack and other platforms to track information related to tasks.
Project Manager at IT CARE
Unified task management enhances team collaboration
What is our primary use case?
What is most valuable?
The most useful features are the Kanban dashboard, the ability to create tasks, bugs, epics with child issues, time estimation, and Jira reports. The dashboard helps in tracking tasks and projects easily. Time estimation is crucial for my team to estimate tasks accurately, and the monthly reports are helpful for monitoring progress. We can see everything in one place, which improves communication within the team.
What needs improvement?
Sometimes it's hard to set up the dashboard for the team lead. For example, I can see tasks selected for development but not UAT tasks. It would be beneficial if the setup was easier. I understand Jira is a comprehensive tool, but dashboard setup could be made more user-friendly.
For how long have I used the solution?
We've been using this solution for about two years already.
Buyer's Guide
Jira
August 2025

Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: August 2025.
866,391 professionals have used our research since 2012.
What do I think about the stability of the solution?
The stability of Jira is good. I have faced issues only once. I would rate it nine out of ten.
What do I think about the scalability of the solution?
Jira is pretty stable and scalable. On a scale of one to ten, I would rate it nine for scalability.
How are customer service and support?
I haven't contacted customer support yet.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
My company also uses Azure DevOps dashboard. I prefer Jira because its interface is simpler and easier to use than Azure.
How was the initial setup?
I am just a user of Jira. The dashboard setup is done by our team lead, so I'm not sure how to set up Jira.
What's my experience with pricing, setup cost, and licensing?
The price is regular for this kind of tool. However, my company hasn't bought Confluence integration because of the price. We are fine with Jira, but would like to have integrations if it becomes cheaper.
What other advice do I have?
Feel free to try it, and you will love it. The biggest advantage is that you can see all of the project in one place on the dashboard, track your estimation and time, and see your progress. I rate Jira 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: My company does not have a business relationship with this vendor other than being a customer.

Software developer at TAIGLE LLC
Provides built-in integrations with different tools, but the configuration process could be less time-consuming
Pros and Cons
- "The scrum dashboard is the product's most important feature. It provides an overview of tasks, who is working on what, and the status of each task."
- "The solution heavily focuses on the Agile framework, which might only suit some business use cases. This particular area needs enhancement."
What is our primary use case?
We follow an Agile framework and use Jira for sprint planning and management.
What is most valuable?
The scrum dashboard is the product's most important feature. It provides an overview of tasks, who is working on what, and the status of each task.
It offers very good APIs for creating custom integrations and has many built-in integrations with other tools.
What needs improvement?
The solution heavily focuses on the Agile framework, which might only suit some business use cases. This particular area needs enhancement.
For how long have I used the solution?
I've been using Jira for about three years.
What do I think about the stability of the solution?
The platform is very stable. I haven't faced any stability issues with it.
What do I think about the scalability of the solution?
Approximately 70 to 80 people are using Jira in our organization. It is a scalable product.
How was the initial setup?
Setting up Jira takes some time. You need to create dashboards, configure settings, and test those configurations. The default setup is straightforward, but understanding and applying the various configurations can be time-consuming.
What other advice do I have?
For smaller organizations, it might be better to consider alternatives like Linear.io. But if you need an integrated system, especially with other Atlassian products, Jira is a solid choice.
It is widely used, so the transition is easier if someone moves from one organization to another that also uses it. Additionally, its automation features are powerful and can address many use cases.
The reports are useful, giving an overview of a sprint's progress and indicating areas for improvement. However, I have yet to use the analytics feature much.
I rate it a seven out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Jira
August 2025

Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: August 2025.
866,391 professionals have used our research since 2012.
Senior Manager, Connected Home Product Management and Strategy at a consultancy with 10,001+ employees
An affordable solution. for communication with easy maintenance
Pros and Cons
- "Everything is tracked in one place."
- "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."
What is our primary use case?
We maintain all space-related information in Jira. We track all stories and add tasks to identify specific services. We pull the relevant functions onto the screen. We follow a two-week sprint cycle, completing sprints accordingly. We proceed to make a release. We conduct testing activities, whether manual or automated. If bugs are identified, we fix them. The customer story remains in the loop until we move to the release cycle. Upon release, developers can automatically deploy the code. After deployment, we proceed with user acceptance testing and move to the front end.
What is most valuable?
Everything is tracked in one place.
What needs improvement?
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.
Additionally, Jira analytics needs further development to analyze code, but we should keep the queries. This will allow us to delve into the details of completed tasks, work in progress, and pending items. However, more information regarding graphical representation is still required. Considering the number of test cases, it's crucial to have comprehensive data on completion status, logs, and retesting. Jira excels in providing such detailed information.
For how long have I used the solution?
I have been using Jira for 6 years.
What do I think about the stability of the solution?
The product is stable.
I rate the solution’s stability a nine out of ten.
What do I think about the scalability of the solution?
The solution’s scalability is good.
55 users are using this solution every day.
I rate the solution’s scalability an eight out of ten.
How are customer service and support?
We receive technical support. Some challenges may arise, particularly in labels, but we receive assistance.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I have used ALM before. It has high pricing, considering the maintenance and shipping costs. Although the features are new, if we compare them to Jira, ALM still lags.
How was the initial setup?
The initial setup is easy and takes a few hours to complete.
I rate the initial setup a nine out of ten, where one is difficult and ten is easy.
What about the implementation team?
A third-party vendor handles deployment. They will automatically execute the small instructions. Based on that, they will create a charge code, seek approval from management, and then proceed to deploy the particular feature. While auto-deployment is happening, we'll validate it once it's done. If everything is good, we'll release it. If there are any challenges, we'll roll it back.
What's my experience with pricing, setup cost, and licensing?
The product is cheap.
I rate the product’s pricing one out of ten, where one is cheap and ten is expensive.
What other advice do I have?
Jira is easy to use and maintain; everything is in one place. Minimal maintenance is also required.
We have our developers to maintain Jira. They will develop whatever we require for labels and provide them to us.
If you want to inform me about the adaptations for scaling Jira, it will be convenient to use Jira, but most of the reports will be easy to generate. We integrate with Git, making the process a bit easier.
Overall, I rate the solution a ten out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Python Developer at Crosslynx
An affordable tool with an easy initial setup phase
Pros and Cons
- "The product's initial setup phase is easy."
- "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."
What is our primary use case?
I use Jira in my company for my projects or the tasks assigned via the tool. I also use Jira as a scrum tool.
What is most valuable?
The solution's most valuable feature is that I used the tool to deal with bugs. In my project, with the bug assigned to me by my company, I was given the backlog and the code. Whenever I had to add it, I used to request Git for code push, pull, and merge, and then I used to paste that GitID into Jira. It was very easy for the other developers to handle whatever code I did.
What needs improvement?
At times, I am not able to report a bug. 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.
For how long have I used the solution?
I have been using Jira for two years. My company is a customer of the tool.
What do I think about the stability of the solution?
It is a stable solution. Stability-wise, I rate the solution a nine out of ten.
What do I think about the scalability of the solution?
Scalability-wise, I rate the solution an eight out of ten.
With the latest versions being released, I feel Jira is being improved daily.
My previous organization used Jira, and now, my current company also uses it.
How are customer service and support?
The solution's technical support needs just to understand the customers' environments and improve or provide a better version of the tool. I rate the technical support a nine out of ten.
How would you rate customer service and support?
Positive
How was the initial setup?
The product's initial setup phase is easy.
The solution is deployed on the cloud.
What's my experience with pricing, setup cost, and licensing?
It is an affordable tool.
What other advice do I have?
From a project management perspective, my project manager assigned some Jira tickets, and I started to do it on a weekly and daily basis. I send a request to a Jira ticket to open it, and during the process, I start describing how I am replicating that issue, explaining it in that Jira ticket. After that, I resolved that Jira ticket put that Git code in the expression part, and submitted it.
Regarding reporting and analytics features, my company uses Jira for software development projects as if it were a single tool. My company uses the tool in a manner where we send requests to one developer, and they open a Jira ticket using the email. Every day, they update so that everybody is able to see it without any description, while my team can see what the developer is doing daily. If a developer is updating, everybody can see that in the company. The tool is very easy to use, and it is easy to understand areas like script planning, story points, and backlog grooming.
I recommend the product to those who plan to use it. I worked with two scrum tools. In Azure also, my company uses scrum, which is a little bit uncomfortable for me, but I am very comfortable with Jira, a major reason I suggest it to other people.
I rate the overall tool a nine out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Dev Ops Engineer at a wellness & fitness company with 201-500 employees
One-stop solution for requirement gathering with moderate pricing
Pros and Cons
- "It's easy to use, and it also offers excellent notifications."
- "It lacks features to cover all testing aspects, so we often integrate it with other plugins or tools like X-ray."
What is our primary use case?
We use it for requirements gathering. We raise our tickets; it takes tickets in the engine. We also use it for bug tracking and integrate it with the X-ray for testing.
What is most valuable?
Jira is a one-stop solution for all the requirements of an Agile project, including SSL. It's easy to use, and it also offers excellent notifications.
What needs improvement?
Jira has integrations with almost all other build management and alerting tools, both open-source and licensed ones. There are limitations to its data.
It lacks features to cover all testing aspects, so we often integrate it with other plugins or tools like X-ray. It would be beneficial if Jira included modules covering testing elements such as test planning, mapping test cases to requirements for traceability, tracking execution status, and managing different branches before release. Since Jira lacks robust support in these areas, we rely on additional tools like X-ray, which can be integrated with Jira. If Jira could incorporate these features internally, our processes would be streamlined.
For how long have I used the solution?
I have been using Jira for 5 years. We are using the latest version of the solution.
What do I think about the stability of the solution?
I rate the solution's stability an eight out of ten.
What do I think about the scalability of the solution?
Around 100 users are using this solution. It is scalable too.
I rate the solution's scalability an eight out of ten.
How are customer service and support?
Customer support is good.
How would you rate customer service and support?
Positive
How was the initial setup?
Jira is not difficult to install. We have an IT help desk team to take care of admin configurations, installations, etc. Everything is managed by different teams.
There are roughly around 50 people for deployments or maintenance overall.
What about the implementation team?
What's my experience with pricing, setup cost, and licensing?
The product is moderate and has a yearly subscription.
I rate the product's pricing a five or six out of ten.
Which other solutions did I evaluate?
I have used some other test management tools, such as ALM. If it is a full model, it'll be too difficult to manage in Jira, but for Azure projects, Jira is the best. It depends also on the needs of the project.
What other advice do I have?
My advice would be to consider having a Jira license. There's a level of customization available, along with flexibility in pricing plans, so you can tailor your request according to your needs. This allows us to access features that align directly with our requirements.
Jira has integration capabilities with almost all build management and alerting tools. It offers seamless integration with both open-source solutions and licensed ones.
Overall, I rate the solution a ten out of ten.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Project manager
A tool that provides visibility and streamlines processes in an organization
Pros and Cons
- "The product's initial setup phase was straightforward."
- "I want Jira to have more plug-ins, which will allow for more free plug-ins that help with the area of reporting."
What is our primary use case?
I use Jira in my company as a project management and software development tool. We use Jira in our company to document all of our requirements and releases in relation to project management and manage the agile lifecycle management of our products.
What is most valuable?
The most valuable feature of the solution is that it is easy to use and allows users to use agile methodology. Jira also offers a lot of plug-ins, which are helpful.
What needs improvement?
I would love to have more free plug-ins in the solution since most of its present plug-ins are great. I want Jira to have more plug-ins, which will allow for more free plug-ins that help with the area of reporting.
For how long have I used the solution?
I have been using Jira for four to five years.
What do I think about the stability of the solution?
It is a stable solution as it is a cloud-based product.
What do I think about the scalability of the solution?
It is a scalable solution, but it comes with an extra cost.
More than 100 employees in our company use the solution.
My company has not faced any problems or issues with the use of the solution. That tool's use can be easily extended.
As everybody in the organization has a role in the use of the product, employees ranging from managers to developers use it.
How are customer service and support?
My company has not faced issues with the use of the solution. It is very easy to reach out to the technical support team of the product if our company faces any issues with the product. My company just needs to schedule a call with the technical support team of the product, and they readily help us. The solution's technical support is good.
Which solution did I use previously and why did I switch?
I have worked with some other tools in the past. My company chose Jira since it was easy to use, scalable, and pretty straightforward.
How was the initial setup?
The product's initial setup phase was straightforward.
The product's deployment phase was straightforward, as one just needs an account to log in. As not many technicalities are involved in the product's deployment process, it is useful for project lifecycle management.
The solution is deployed on the cloud. Jira also allows users to opt for an on-premises deployment model.
What's my experience with pricing, setup cost, and licensing?
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.
What other advice do I have?
It is a perfect tool for those who want to manage the projects in their organization.
The benefit I have seen from using Jira is that it streamlines the development process. In general, the solution provides visibility and streamlines processes.
I rate the overall tool an eight out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
IT Manager at a government with 10,001+ employees
Easy to use and easy to onboard, but needs better documentation and better integration with other tools
Pros and Cons
- "It was easy to use. The consultants that we had on board were familiar with it. So, obviously, having a community that had used it before or was familiar with it was a positive thing."
- "If I'm comparing it to ALM Octane, the documentation is not as robust as ALM Octane's documentation. So, they can improve on the documentation side."
What is our primary use case?
We had a regulatory requirement through our legislature to collect motor or voter information for residents of California. So, if you basically wanted to sign up to vote, you could do so at a department of motor vehicles. The Jira instance was used for what we call the new motor voter, which is the online premise to register to vote when you conducted a DMV transaction, such as vehicle registration, driver's license, renewal, etc.
We had its latest version. It is online. In the cloud, we set up an account for the department, and then add users as needed. It is a government cloud.
How has it helped my organization?
It documented our business requirements.
What is most valuable?
It was easy to use. The consultants that we had on board were familiar with it. So, obviously, having a community that had used it before or was familiar with it was a positive thing.
What needs improvement?
If I'm comparing it to ALM Octane, the documentation is not as robust as ALM Octane's documentation. So, they can improve on the documentation side.
Another enhancement could be in the area of interfacing with other products or connectivity. It could have better integration with other tools.
For how long have I used the solution?
I have been using it since 2017. It has been about five years.
What do I think about the stability of the solution?
Its stability is good. There are no issues with the performance.
What do I think about the scalability of the solution?
Its scalability is fine. At the peak, we had about 15 users, and towards the end, we had five users.
Our usage was not extensive. We used it only for one project, which was the motor voter project. We don't have any plans to increase the usage. We have stopped paying the subscription fee from the last month because we migrated everything over to ALM Octane for our business requirements.
How are customer service and support?
We didn't need to call them at all.
Which solution did I use previously and why did I switch?
We were using IBM DOORS Next Generation for business requirements. It was on-premises, and we weren't able to make it available through a URL to the external consultant or workforce. That's why we basically went with Jira. IBM DOORS Next Generation wasn't flexible enough to accommodate all of our remote workforce.
How was the initial setup?
It was straightforward and easy. You basically create an account for your department, and then you onboard your users. There is a subscription fee per user for each month through Confluence.
It took us a week to get it up and running. It involved reading, studying it, figuring it out, and then doing it. It was pretty simple to set up data and add users. So, we onboarded it within a week.
The challenge for us while setting it up was that we had to put it on a credit card, which is not a good thing for the government. Typically, the government likes to pay through a purchase order or procurement process, but because it was a monthly subscription fee, it had to be on a credit card. We had to use an executive card in order for us to pay the bill every month, which was really kind of a pain because our accounting office always had to make sure and check the number of users. They would ask if I had 15 users this month. I am the administrator of the application, so, of course, I know how many users are there. I can see how many users are there and how many are using it and remove them if they don't. I think the state just needs to modify its procurement process because I think ours is pretty old school. I don't think that Atlassian needs to adapt to ours, but that was the only challenge we had in setting it up and configuring.
What about the implementation team?
We had an in-house as well as a procured consultant, but he was through the state, not directly with Jira or Confluence.
What's my experience with pricing, setup cost, and licensing?
The ballpark figure is about $100 a month.
What other advice do I have?
It is easy to use and easy to onboard. It has got a good foundation of offerings for the business requirements if you're working on an agile project or user stories.
I would rate Jira a seven out of 10.
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: My company does not have a business relationship with this vendor other than being a customer.
Information Technology Program Manager at Reframe Solutions
A very comprehensive, flexible product; premium version offers great advanced planning features
Pros and Cons
- "A very comprehensive product; easy to set up and is very user-friendly."
- "Lacks field-level permission in the cloud version."
What is our primary use case?
I personally use Jira for project management and agile software development. I'm an information technology program manager and we are customers of Jira.
How has it helped my organization?
We're a software development company and Jira is an essential element of our daily work. We wouldn't be able to function without it.
What is most valuable?
Jira is a very comprehensive and flexible product. It's easy to set up, easy to learn, and is very user-friendly. If you're using the cloud version from Atlassian, there are no issues with maintenance or performance. I especially like the advanced planning features in the premium version and there are plenty of apps available if any functionality is missing.
What needs improvement?
The only complaint I have about Jira is that there is no field-level permission for the issues in the Jira cloud version. You can get an app for the server version, but the cloud version doesn't allow that type of functionality. For example, I write a user story that goes to the customer for approval. Once approved, I would want to be able to lock the description for that user story so it can't be changed, but I'm unable to do that. I can lock the whole story but not the description alone. It creates a problem because when I need to add the story to a sprint, I need to change the sprint number field. It can't be done because the whole issue is locked or lacks the properties to be edited.
The other thing missing is a straight connection to the pipelines and the source control. I think it should be integrated with GitHub and other products that developers use. It's the lack of integration that's the main reason we are considering moving to Azure DevOps.
For how long have I used the solution?
I've been using this solution for several years.
What do I think about the stability of the solution?
I haven't had a single issue with Jira.
What do I think about the scalability of the solution?
Jira is easily scalable to any level you want. Our company has 60 to 70 users working on multiple projects and we have a second installation specifically for one of our customers which has around 25 users. The users in our company have traditional roles; developers, business analysts, QA engineers, project managers and customers. We're using it constantly.
What's my experience with pricing, setup cost, and licensing?
Jira has a two-tier pricing system; a basic level and a premium level, which I think could be broken down a little more, but the pricing and billing are reasonable. You can add or remove users and they bill you dynamically month to month based on the number of users. It would be nice to have tiered pricing based on user numbers because, for large companies with hundreds of users, it's going to become expensive really quickly. It's acceptable for us and we have what we need.
Which other solutions did I evaluate?
We are considering switching to DevOps and are currently carrying out an evaluation. The main reason is that our offshore team uses DevOps for everything. We started with Jira so they had to use it for us, but we're hearing that DevOps is better integrated with source control and releases, so it's something we're considering now.
I've had a look at the pricing of DevOps and it's really strange. Basic pricing is $6 per user per month or if you want to include test plans it jumps to $52 per user per month, which is an astronomical jump. I'm not sure whether it's $52 for every single user on the system. Jira charges $7 per user, per month for the basic version or $14 per user, per month for the premium one.
What other advice do I have?
The product is very useful. As a program manager, I recommend it wholeheartedly. The cloud version is easy to set up, and there's no maintenance required. I haven't incurred any issues with performance or updates being applied incorrectly or any bugs.
I rate the solution nine out of 10.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.

Buyer's Guide
Download our free Jira Report and get advice and tips from experienced pros
sharing their opinions.
Updated: August 2025
Product Categories
Application Lifecycle Management (ALM) Suites Application Requirements Management Project Management SoftwarePopular Comparisons
Microsoft Azure DevOps
monday.com for Enterprise
IBM DOORS
OpenText Application Quality Management
Codebeamer
Polarion ALM
Jama Connect
TFS
Rally Software
Asana
OpenText Software Delivery Management
Jira Align
Polarion Requirements
Microsoft Project
Broadcom Clarity
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?