No more typing reviews! Try our Samantha, our new voice AI agent.
Team Lead - Web Services at a manufacturing company with 10,001+ employees
Real User
Dec 8, 2021
Highly scalable with excellent speed and search capability
Pros and Cons
  • "No other platform can compete on speed or search."
  • "Jira is easier to configure than other platforms like DevOps, is fairly easy to learn so long as you dedicate some time to it, and is easier to use than other solutions."
  • "Some small issues with stability."
  • "The main area for improvement is the high cost of the product."

What is our primary use case?

My primary use case of Jira is as our project management tool for monitoring and planning.

What is most valuable?

The most valuable features are the speed and especially the search capability - I don't think any other platform can compete on those.

What needs improvement?

The main area for improvement is the high cost of the product.

For how long have I used the solution?

I've been working with Jira for two years.

Buyer's Guide
Jira
October 2026
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
922,349 professionals have used our research since 2012.

What do I think about the stability of the solution?

There are some small issues with stability, like unexpected updates, but overall it's good.

What do I think about the scalability of the solution?

I think you can scale Jira as far or as big as you want, it's very scalable.

How are customer service and support?

Jira's technical support is easy to communicate with, and they are very responsive.

What's my experience with pricing, setup cost, and licensing?

This product's cost is much higher compared to other platforms, but it's worth the extra cost. Some add-ons are only available at additional cost.

What other advice do I have?

Jira is easier to configure than other platforms like DevOps. It's fairly easy to learn so long as you dedicate some time to it and is easier to use than other solutions. I would rate this solution as nine 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.
PeerSpot user
Software Architect at AIOPS group
Real User
Dec 1, 2021
Trustworthy, convenient, and flexible
Pros and Cons
  • "It is a very convenient tool. We can organize our sprints through scrum or kanban. There are scrum boards, and there are kanban boards. If you prefer scrum, you can use Jira. If you prefer kanban, you can still use Jira. You can create your kanban boards in a similar way as you create your scrum boards. It is very useful. It also seems to be very popular these days."
  • "It covers most of the development process, and almost everyone uses it, from business owners and product owners to testers, developers, and DevOps, with all features, stories, tasks, and test cases managed in Jira so everything is done in Jira."
  • "Its search and reporting can be improved. They are already nice, but they can be further improved."

What is our primary use case?

We are using it to organize most of our software development processes. 

Being a cloud solution, we usually have the latest version, but sometimes, we get a pop-up saying that there are some changes in a menu or some new features are there.

How has it helped my organization?

It covers most of the development process, and almost everyone uses it. We are using it for every role involved in the project, such as business owners, product owners, testers, developers, and DevOps. For example, the product owner defines a new feature, and then we take the feature and create stories and development, testing, or DevOps tasks. We then implement the new feature or changes to an existing feature. All the test cases and other things are in Jira. So, everything is done in Jira.

What is most valuable?

It is a very convenient tool. We can organize our sprints through scrum or kanban. There are scrum boards, and there are kanban boards. If you prefer scrum, you can use Jira. If you prefer kanban, you can still use Jira. You can create your kanban boards in a similar way as you create your scrum boards. It is very useful. It also seems to be very popular these days.

What needs improvement?

Its search and reporting can be improved. They are already nice, but they can be further improved.

For how long have I used the solution?

I have been using this solution for more than 10 years.

What do I think about the stability of the solution?

Its availability is great.

What do I think about the scalability of the solution?

We have different offices, and overall, there might be about 2,000 people. There are no issues with its performance or service. Almost all roles in our company are using this solution.

How are customer service and support?

Other people have experience with Jira's technical support, and they are quite happy with their support. Personally, I never had a case where I needed any kind of support.

How was the initial setup?

It is a cloud solution. It just requires licensing. Of course, some support would be required for all users of Jira, which could be in thousands. It might not be an easy task, but overall, I don't think a lot of time is spent on its maintenance and support. It is a very trustworthy service.

What's my experience with pricing, setup cost, and licensing?

It is certainly a long-term solution for our company and for previous companies that I have worked for. They have these long-term term licenses, but I'm not sure if they really pay on a yearly basis. They are certainly using it for a really long period and for a lot of users.

What other advice do I have?

I would definitely recommend this solution. It is very popular, and a lot of my colleagues have used it before. It doesn't require a lot of learning time. It is very good to use. I'm quite happy with the service. Of course, it can improve, but personally, I'm very happy with it.

I would definitely give it a good rating. I would rate it a 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.
PeerSpot user
Buyer's Guide
Jira
October 2026
Learn what your peers think about Jira. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
922,349 professionals have used our research since 2012.
Senior Manager at Capgemini
Real User
Nov 29, 2021
Solid solution for agile, iterative, and incremental development
Pros and Cons
  • "The burndown chart is also helpful when it comes to reporting and allows us to know where we are going, especially during development."
  • "It is a good solution and a very popular one, as well, so I would recommend it if you are going for agile methodology."
  • "The initial setup was a bit problematic in terms of getting access to Jira. That goes for a few users, including me."

What is our primary use case?

My primary use case for Jira is agile development as a systems integrator. The best use case is to pile up the backlog and then assign those backlogs stories to the user stories, which will be filtered into a sprint. Each story is then assigned to a cross-functional team member for tracking the dependencies and progress on the user story. You can also tag the user story to a particular team.

What is most valuable?

The most valuable feature for me has been tagging. Also, there's the option to add task lists to each user story. In addition, user stories can be grouped into one feature, which allows us to visualize our progress. The burndown chart is also helpful when it comes to reporting and allows us to know where we are going, especially during development.

For how long have I used the solution?

I have used Jira for a total of seven months. 

What do I think about the stability of the solution?

Jira is a reliable solution. In fact, it is not only used for user stories. It is used as an issue tracker tool as well. So I think it supports multiple use cases, which is good.

What do I think about the scalability of the solution?

Multiple users have logged into it at the same time without running into any issues. At my current organization, some 25 people use it. At my previous organization, about 40 people used it. We have plans to increase usage. 

How are customer service and support?

I have not had to call up their tech support. They have plenty of troubleshooting documentation online. 

How was the initial setup?

The initial setup was a bit problematic in terms of getting access to Jira. That goes for a few users, including me.

What other advice do I have?

It is a good solution and a very popular one, as well. So I would recommend it if you are going for agile methodology. It works for both iterative and incremental development. You should use it. 

This is a solid solution for medium to large companies.

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.
PeerSpot user
Automation Architect at Micro Focus
Consultant
Nov 9, 2021
Useful dashboards, effective reports, and updates quickly
Pros and Cons
  • "The dashboard and reports tracking and the setup updates quickly, I am very impressed with those features, and additionally, it is user-friendly."
  • "The integration of Jira could improve. The solution should be able to integrate easily with other solutions, such as ERPs. There are times the solution can be slow and we have to reset it over and over again."
  • "The scalability has to be improved more because Jira currently is similar to a standalone solution with very limited integration."

What is our primary use case?

We are using Jira for requirement and defect management. Not for DevOps purposes, only application development.

What is most valuable?

The dashboard and reports tracking and the setup updates quickly, I am very impressed with those features. Additionally, it is user-friendly.

What needs improvement?

The integration of Jira could improve. The solution should be able to integrate easily with other solutions, such as ERPs. There are times the solution can be slow and we have to reset it over and over again.

In an upcoming release, they should improve the user management features. For example, when I want to monitor a project as a CEO I do not want all the details but enough that I can understand. Additionally, these features should be accessible to me by mobile.

For how long have I used the solution?

I have been using Jira for approximately two years.

What do I think about the stability of the solution?

Jira is a reliable solution for that medium-sized organizations. It's not for enterprise-level organizations, they have a long way to go.

What do I think about the scalability of the solution?

The scalability has to be improved more because Jira currently is similar to a standalone solution with very limited integration. The integration with other products has to be more.

We have approximately 50,000 people using the solution.

How are customer service and support?

We use our own IT department for the technical support of Jira.

How was the initial setup?

The initial setup was complex.

What's my experience with pricing, setup cost, and licensing?

We used to be on a perpetual license provided by our clients.

What other advice do I have?

I would recommend this solution to others. Any new startup company can start with Jira immediately because it is now offered in the cloud.

I rate Jira a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
reviewer927504 - PeerSpot reviewer
Senior Technical Project Manager at a financial services firm with 10,001+ employees
Real User
Oct 22, 2021
Very extensible with ability to integrate other tools and different interfaces into it
Pros and Cons
  • "Offers a common language set so we can bring people into projects and get them up and running almost immediately."
  • "The benefit of Jira to our company is that the product is extensible."
  • "Although this is a somewhat old-school approach, we'd like to see some common building block approaches to certain things."

What is our primary use case?

Similar to the whole solution stack, we use Jira for security and for operational data storage. We also use it for custom-made API structures, moving data from the cloud to legacy on-prem infrastructures so we can use it to develop failing interfaces. We're customers of Jira and we license the solution. Our company has a form of strategic alliance where we buy the product, pay the fees and use the solution. I'm a senior technical project manager.

How has it helped my organization?

The benefit of Jira to our company is that the product is extensible. We can integrate other tools and different interfaces into it. You can look at what's being done, how it's being done and know how to improve it. That includes things like optimizing performance or scanning the structures we build for security vulnerabilities. Extensibility is the most effective way we can create products and services for our clients.

What is most valuable?

The value of this product is that it offers a common language set so we can bring people into projects and get them up and running almost immediately. We know the language. It's the training and education content that's key and there's enough out there, whether it's paid training or free training, that gets people up to speed pretty quickly. Following on from that is optimizing the training for a given initiative or project. 

What needs improvement?

Although this is a somewhat old-school approach, we'd like to see some common building block approaches to certain things. We do a lot of coding and swapping things because there's a lot of common non-functional capabilities we have to share based on our own company policies. In that sense, it would be helpful to have some sort of modular building blocks that are in some of these up-and-coming extensible capabilities, like how you interface the next level of security scanning code or cloud to cloud capabilities, anything like that would be an improvement. These are expensive things to build and give out for free. At least knowing what's in the headlights for the products together with some good specific industry demos would help, whether related to the financial sector, healthcare sector, whatever. There isn't a lot of that; as things stand, they're generally offering demos with people talking about how you could have a secure way of developing a code for a HIPAA mixed standards or whatever. More documentation on how to precisely use the solution, particularly in a given industry sector, would be helpful.

We use a lot of third-party monitoring and although the extensibility is there, a monitoring tool suite as you get in production would be helpful. 

For how long have I used the solution?

I've been using this solution for 10 years. 

What other advice do I have?

This is a good product, it's served us well. I don't really have a lot of issues with it so I rate the solution eight out of 10. 

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.
PeerSpot user
it_user1695474 - PeerSpot reviewer
Software Engineer at a financial services firm with 10,001+ employees
Real User
Oct 20, 2021
Provides high visibility into the development pipeline
Pros and Cons
  • "We have been able to integrate the ecosystem we created using this automation tool, so when we run the Jenkins pipeline, the build is already automatically connected to Jira."
  • "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."
  • "There are times when Jira goes down, and we find it difficult to log in."

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
PeerSpot user
Sr Project Manager at ITM LLC
Real User
Oct 12, 2021
Streamlines the process of managing our projects, brings transparency, and is lightweight and easy to use
Pros and Cons
  • "Overall, it is very intuitive. It is so lightweight and easy to use. It is easy to manage our product backlog and user stories, and it produces great reports."
  • "It definitely streamlined the process of managing the projects."
  • "It is not capturing the number of hours for which each person has worked on certain things. We use many add-ons to let resources enter the time in the user story itself. We use an add-on called Tempo, but it is kind of a lousy add-on. It is not straightforward. Rather than helping us, it creates a lot of confusion. So, instead of looking out for the additional add-on, I would prefer to have the timesheet entered as a part of Jira itself. They are anyways capturing every information they could for each user story, and then we are able to break down all the task lists. For each task, we're also assigning a resource. So, while we're doing it, why can't they allow the users to enter the time that can be created as a report? Right now, we need to acquire the add-on, and the add-on is not great. It is not helping. The add-on is also not free."
  • "We use an add-on called Tempo, but it is kind of a lousy add-on. It is not straightforward; rather than helping us, it creates a lot of confusion."

What is our primary use case?

I use it to manage my scrum projects and some of the Kanban projects.

In terms of version, they have been updating it every three weeks. It is a kind of a sprint that they do, just like Google Chrome. So, there is no going back and forth. We use a cloud-based application. So, it is always the updated one.

The type of cloud depends on the client. I've been through all kinds of situations: completely public, semi-public, and private. If it is a public cloud, then it is directly from Atlassian. They are providing it. So, there is no middleware.

How has it helped my organization?

It definitely streamlined the process of managing the projects. Earlier, we had a system scattered all over the place. We had information in Excel, Microsoft Project, and some of the other applications that we have, but now, we have everything in Jira itself. So, we create user stories and groom the product backlog. We have kept everything in Jira. It is our single source for project information that anyone can go to. So, we could see a lot of transparency with Jira.

What is most valuable?

Overall, it is very intuitive. It is so lightweight and easy to use. It is easy to manage our product backlog and user stories, and it produces great reports.

What needs improvement?

It is good for single projects, but if you have to manage the portfolio level of the projects, they have a few add-ons that we need to buy and integrate. They can improve this part to manage it in a better way.

It is not capturing the number of hours for which each person has worked on certain things. We use many add-ons to let resources enter the time in the user story itself. We use an add-on called Tempo, but it is kind of a lousy add-on. It is not straightforward. Rather than helping us, it creates a lot of confusion. So, instead of looking out for the additional add-on, I would prefer to have the timesheet entered as a part of Jira itself. They are anyways capturing every information they could for each user story, and then we are able to break down all the task lists. For each task, we're also assigning a resource. So, while we're doing it, why can't they allow the users to enter the time that can be created as a report? Right now, we need to acquire the add-on, and the add-on is not great. It is not helping. The add-on is also not free.

There could also be some additional reports.

For how long have I used the solution?

I have been using Jira for seven to eight years.

What do I think about the stability of the solution?

Stability-wise, it is very good. It is very lightweight. I have used other enterprise-level products to manage the same kind of scrum and Kanban projects and other projects. Other products have many enterprise-level features, but they're very slow and kind of hard to manage.

What do I think about the scalability of the solution?

It is a cloud-based one, so I don't see much difficulty in scaling it. If you want to go from 100 users to 200 users, you will be able to do it without much hassle.

I've been doing a lot of consulting. So, I've seen from five users to the entire organization with more than 500 people using it.

How are customer service and support?

I did contact them through email and discussion forums. I had a limited opportunity to work with them. So, I don't know much about their support.

Which solution did I use previously and why did I switch?

Jira is a kind of the last one I settled on. Before that, I have used products such as Rally and VersionOne. These two are enterprise-level scrum and Kanban tools that are similar to Jira. 

I have also used Asana and Trello. Trello is lightweight, but I wouldn't call it equivalent to Jira. Jira has many features that not many solutions have. 

How was the initial setup?

Most of the time, we are working with the cloud-based one. So, we don't have to set up everything. It is all there. You just buy a monthly subscription package. The workflow configuration, however, would be a bit difficult while you're trying to set it up. In addition, if you have to go down to the permission level, it is a bit different.

What other advice do I have?

Workflow-wise, you need to plan well because once you configure it, you cannot often change a workflow. For each project, the workflow might be different. You might have a development team, a QA team, a configuration team, and a deployment team. When you start a task, you just need to make sure you are covering everyone. In terms of the workflow, you should know what would happen if someone is not there, and what are you going to do. So, you need to make sure that you are covering those things. Other than that, you need to know how much you are going to take care of the hierarchical level permissions. These are two primary things, and then, later on, you can relabel quite a lot of things in terms of how you're using the backlog product and user stories.

I would rate Jira an eight out of 10.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
reviewer1690113 - PeerSpot reviewer
Product Engineering & Operations Director at a tech services company with 10,001+ employees
Real User
Oct 10, 2021
Dynamic and easy to use but needs better API integration
Pros and Cons
  • "In terms of the general way that the tool functions, it seems like it's a pretty good fit-for-purpose for what we're trying to do, and we've never thought about replacing it with another technology."
  • "We're doing PI planning, Program Increment planning, and that kind of stuff, and it's not always a good facilitator for that. We tend to pull it out and put it into other tools to manage that, and then we get it back into Jira as that's our system of record for where all the stories are kept. That's probably the biggest headache with it."

What is our primary use case?

It's pretty much for engineering development, Scaled Agile purposes for engineering development, for managing basically the epics and the stories and the capabilities and everything that we have to deliver in sprints. We're not using it as a ticketing tool or anything like that, for operations. We're using it purely for managing the development stuff in a Scaled Agile manner.

What is most valuable?

The solution is easy to use. It's pretty dynamic. It allows us to basically handle everything that we need in terms of a backlog, and we're trying to do it in an organized manner, so we know who works on what and how to size the story points so we can ensure that our epics burn down from sprint to sprint.

In terms of the general way that the tool functions, it seems like it's a pretty good fit-for-purpose for what we're trying to do. We've never thought about replacing it with another technology. 

The initial setup is pretty straightforward. 

The stability is pretty good.

What needs improvement?

There are a few things about it that I think need to be improved in terms of the ability to build reports. We would like to be able to use the data from Jira to help drive Gantt chart roadmap-type views of not only what we're building, but rather where we're going.

What we've elected to do in a couple of cases is just pull the data out of Jira and then pull it into Power BI so that we can try to get some of the more sophisticated information that we want out of it. We actually experimented with building portfolio views so we can see stuff in real-time. In some ways, it's okay. In some ways, it's just a little lethargic for our purposes.

We'd like to be able to manage things in real-time and by looking at stuff. We're doing PI planning, Program Increment planning, and that kind of stuff, and it's not always a good facilitator for that. We tend to pull it out and put it into other tools to manage that, and then we get it back into Jira as that's our system of record for where all the stories are kept. That's probably the biggest headache with it.

For some of the portfolio stuff that we did, the queries were so complicated that it was just taking forever. It was like watching paint dry for the results to come back. We would be in a meeting and then we'd hit a refresh and you're waiting for what seems like an eternity.

The solution could use API integration to take feeds from other tools so that we can read them better. We got one camp using an ITBM tool from ServiceNow. We have Jira running in this other area, and having an API between the two so we could actually collaborate between the two tools. However, API integrations with other tools would be helpful so we could either take data out of it or put data in it, thereby making it more of a data-driven platform that integrates nicer with other platforms. That, I think, would be something I would like to see.

For how long have I used the solution?

I've been using the solution for four years or so. 

What do I think about the stability of the solution?

I haven't heard people really complain that it's unstable. We haven't had very many performance issues with it. I don't know if it was a network problem or what it might have been, however, I haven't really heard people talk about performance problems other than when we were trying to use it for portfolio views and that got kind of weird as queries were just complicated. Beyond that, the stability has been fine.

What do I think about the scalability of the solution?

The issues that we have with scalability aren't necessarily with the tool as much as it's how we're using it. We're a big company so there are a lot of people using Jira, however, we don't really see how the projects correlate across different activities within the company. When we're trying to get two integrated roadmaps and trying to get to a point where we're collaborating, doing inter-sourcing of a solution, and we're all in Jira, there are times where we're in it and yet we can't collaborate and work together, and so we start replicating things across the two projects.

I don't know how much of that is the issue with using it how we are versus the product itself though. 

We have 8,000 to 10,000 people using the solution currently. That's across many departments. We are a company of around 150,000 people. There may be people using it that I am not even aware of. I only have visibility of what I'm doing and what I'm exposed to in terms of integration with offerings and that kind of stuff. I know when we were managing licenses, we used to have a DevCloud team. For their scope, it was in the 8,000 to 10,000 user range. 

The solution is being pretty extensively used. Likely usage will grow as the company grows and takes on new business. I don't know if it's going to organically grow exponentially as it's already being used where it needs to be used and currently we're only using it for development activities across the different offerings and platforms. It's not used as a day-to-day run-and-maintain ticketing system to manage customers or issues or anything like that. I'm sure there'll be some incremental growth as we take on new business and grow as an organization.

Which solution did I use previously and why did I switch?

We use Jira. We use Confluence as an extension of that, and then we also use ServiceNow, the ITBM capabilities of ServiceNow as well.

How was the initial setup?

We had a DevOps team that ran our cloud environment, and they basically spun up a project for us, and it was pretty straightforward. It's not like we were installing it in the cloud. People just said, "Here you go, and you can just start using it." After that, we just created a project for what we were doing, and then we were on our way. I wasn't really involved with any part that was problematic or anything.

In terms of maintenance, pretty much everybody is maintaining their own instance. We've got somebody that manages what's in the cloud for the company, however, it's pretty much hands-off in terms of day-to-day support issues. We had a few people that were supporting it when there were problems, however, it's just a handful from what I understand.

What other advice do I have?

We're just customers and end-users.

We are likely using the latest version of the solution. I don't know what the latest version of Jira is, however, I'm pretty confident we are.

The advice I would give is it's not a solution for a novice person that doesn't know Scaled Agile. Users will get out of it what they put into it, and if you don't know what you're doing you could set yourself up for a nightmare when you're using the tool. My advice is that the better you structure yourself and understand Scaled Agile and how you want to set up the project the more successful you'll be at using it for your organization's purposes. If you're going in there as a novice that doesn't understand anything about Scaled Agile you could create a mess for yourself and then it won't give you the value you are seeking.

I'd rate the solution at a seven 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?

Amazon Web Services (AWS)
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
reviewer1675329 - PeerSpot reviewer
IT Manager at a government with 10,001+ employees
Real User
Oct 6, 2021
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."
  • "It is easy to use and easy to onboard, and it has got a good foundation of offerings for the business requirements if you're working on an agile project or user stories."
  • "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.
PeerSpot user
Information Technology Program Manager at Reframe Solutions
Real User
Sep 14, 2021
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."
  • "The product is very useful, and as a program manager, I recommend it wholeheartedly."
  • "Lacks field-level permission in the cloud version."
  • "The only complaint I have about Jira is that there is no field-level permission for the issues in the Jira 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.
PeerSpot user
Buyer's Guide
Download our free Jira Report and get advice and tips from experienced pros sharing their opinions.
Updated: October 2026
Buyer's Guide
Download our free Jira Report and get advice and tips from experienced pros sharing their opinions.