Jira Reviews

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.

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.

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.

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

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.

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.

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

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.

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.

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.

It documented our business requirements.

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.

Another enhancement could be in the area of interfacing with other products or connectivity. It could have better integration with other tools.

I have been using it since 2017. It has been about five years.

Its stability is good. There are no issues with the performance.

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.

We didn't need to call them at all.

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.

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.

We had an in-house as well as a procured consultant, but he was through the state, not directly with Jira or Confluence.

The ballpark figure is about $100 a month.

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.

I personally use Jira for project management and agile software development. I'm an information technology program manager and we are customers of Jira. 

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. 

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.

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.

I've been using this solution for several years. 

I haven't had a single issue with Jira.

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. 

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.

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.

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. 

We are using it for project management.

It helps everyone to be on the same page.

Its integration with Bitbucket, Confluence, and other related products that Atlassian owns is most valuable.

If CI/CD is integrated with it, it would be better. I've used Azure DevOps before, and it's nice to have everything, such as CI/CD Repos and other things, integrated. Jira has fewer integrations. Azure DevOps has an easier interface, and it has got everything in one spot. I don't have to jump around in different applications.

It should have more Trello-like features. There are some things you can do in Trello, but you can't do them in Jira, which doesn't make any sense because Jira bought Trello.

It looks pretty solid.

It looks scalable. I haven't seen any issues.

It is being used extensively at the moment in our organization. Currently, IT departments are using it.

I have not interacted with them.

I wasn't around during the setup.

It has a lot going on. They own Bamboo, but right now, we're using Jenkins. 

I have used Azure DevOps at another company. I would advise going for Azure DevOps because it has everything. You've got your DevOps, and you have your Repos. Everything is integrated.

I would rate Jira a six out of 10.

We have different software projects. I primarily use Jira to define and plan projects for agile-based project management. We use different aspects. We have scrum-based management for some projects and different systems for others.

The agile framework works well, and I pretty much live by that. Everything, such as sprint management, is laid out.

It is easy to use and implement. It provides me with pretty much everything that I need to be able to do day-to-day planning, task management, and work log efficacy.

It is a great centralized tool for everything. You can use it for your local team management to communicate with your developers. You can also use it for your management team and for communicating with subcontractors to keep track of work products, work logs, and perform at the minute status.

For how I identify tasks and break down use cases, I wish there was the ability to drill down Stories multiple levels deep. You have Epics, Stories, Tasks and Sub-tasks. Each of which can go one level deep. It would be nice to be able to be able to define Stories multiple levels deep in order to break down super complex use-cases. That is my only pet peeve. Other than that, they've been improving year to year, and each new version seems to have increased levels of improvement.

I use another product that synchronizes well with Jira called Worklog Assistant, by Sohail Somani, which runs separately to Jira. It is a great product that allows you easily keep track of work performed and generate all respective Jira worklogs at the press of a button. I've been using it for years, and it just makes it very easy for me to keep track of what I am doing with an accurate time tracking mechanism. I think this would be a nice tool to integrated with Atlassian Jira.

I've been using it since 2008.

It is pretty stable. They've improved things over the years. Back in 2008, when we were starting to use it, different issues used to come up from time to time. It was still relatively stable. Now, I rarely run into a problem for which I can say that it is a problem with the tool, as opposed to user error.

It is pretty scalable. I was actually kind of surprised at how much data I can put in. It doesn't slow the tool down. It is quite scalable, and it worked well for the projects that we've done.

We're a small company. I can't compare myself to IBM or Raytheon. I can talk for a small company with up to 45 employees with X number of projects. Because of COVID, we've had to pare down, and currently, we have two users who are using it. I myself use it on a regular basis. Four or five years ago, we had subcontractors who used it with us. At that time, we had seven or eight users, including clients and subcontractors.

It is being extensively used at the moment. The only increase in usage would be to include other individuals on it.

We used their support early on, and they were helpful. At that time, we were using the enterprise product, which was a purchased product. So, as a paying customer, you got straight-up support. They were good. There were some bugs and issues early on that were difficult to get through, but they worked them out. Now, we have fewer people, so we use the one to 10 person option, and I haven't had any reason to call support. I haven't had a need to use their support in years.

They self-use their product for defect management. You can always go to their website and find what's going on. They have forums, et cetera.

In the previous company that I've worked for, I've used Bugzilla for defect management. Task management was in-house, but I don't remember the tool that we used to do task management. For building up sprints, etc, we used a Wiki-based system. It probably was TWiki at the time. We had set up our own Wiki-based environments for doing management, et cetera. We also had Excel spreadsheets. I didn't know about Jira back then in the previous company.

We did some research when I started with this company, and we chose to use Atlassian. It wasn't just, "Oh, the company was using it." It was one of the things that I was part of instituting. We did what we call Decision Analysis and Resolution (DAR) to determine what was the best bang for the buck and what covered our needs, and then it evolved from there. After I started using Jira in this company, a lot of things were easy to do.

Its setup is semi intuitive. There are certain things for which you need to look at the instructions. It also depends on how complex your environment settings are.

Initially, back in 2008, it was a little bit more difficult, but they've improved the installation process. If you have a very basic setup, you can just pretty much install it right out of the box with maybe one or two changes. There're certain things for which you need to have some IT knowledge of your environment in order to be able to set it up. Other than that, they have really automated it pretty well. Jira is one of their keystone products.

Its initial deployment took hours or maybe days because there were things that I needed to understand, but they've improved it a great deal. You can pretty much be up and running within an hour, but it also depends on your environment.

Its implementation was an in-house job.

In terms of maintenance, I take care of its maintenance. Its maintenance is minimum, and only one person is required. You can easily run backups. We use Microsoft SQL Server for backend data management, and we automate the backups. We do daily backups, etc. If anything goes wrong with the tool we have, we can just rebuild it from scratch, and we will be fine because our data is there.

They also have built-in backup utilities that you can use. There is an XML-based one, which I do like to use from time to time just as an alternate. So, you do have different options.

We've seen a return on investment when it comes to Jira.

For very small companies, if you have less than 10 individuals, it is $10 a year for each of the products. When we were a part of the enterprise and had more than 10 people using it, or before they came up with this solution for small companies, it was $2,500 a year for the license for Jira and Confluence, and I believe something like $600 a year to perpetuate the license. I can't remember if it was $600 or $2,500 annually. It was for up to 25 people at the time, and this was in the early 2000s and mid 2000s.

There are a number of add-on products that you can sync with Atlassian Jira. Confluence, FishEye, Crucible, and Bamboo are different Atlassian products, but then there are sub-products. They have what's called Atlassian marketplace, and you can buy products for certain needs. Tempo is a perfect product for doing time management and timesheets. It was also $10. So, you have a bunch of different types of add-on products that different individuals have built that work well with the tool, and they are quite stable.

One piece of advice, which they also give in their documentation, is to use your own database management system. They give you something that you can use. It is called HSQL or something like that, but you can use what your company can afford, such as MySQL or SQL Server, and manage that yourself. It will help you to do better data management and backup management. I would use the built-in backup management system as a backup, although I haven't had any problems at all in years. Just for a warm fuzzy, it is always good to have a backup system.

I would recommend looking into primary tools depending on your needs. If you're doing software, FishEye and Crucible are great products to utilize with it. You also have Confluence and Bamboo for continuous build management. Tempo, of course, is good for certain types of management.

I would rate Jira a nine out of 10.

Jira is used primarily for ticketing, escalations, and tracking work in progress. It is also integrated with other tools within the company. Additionally, we open Jira to customers for ticketing purposes.

Jira is very useful and allows me to know who is in charge, who the owner is, and monitor and track work in progress.

Jira is quite easy to use and very simple from my point of view. It is very useful and direct and allows monitoring and tracking of work in progress. 

It integrates well with other tools in the company and is opened to the customer for ticketing. It is stable with no scalability issues experienced.

The user interface could be improved from a user experience standpoint. It needs to be more visually appealing and customizable to display key data effectively. 

There's room for improvement in the search tool, as it can be challenging to locate tickets directly.

I am quite new to the company and joined one year ago, however, Jira has been used for several years.

It's stable. I have never experienced any trouble concerning scalability or heard from customers about issues related to performance or usability.

Jira is stable, and I have not experienced any issues with scalability. Customers have not reported any problems related to this.

We use Teams officially at the company level, while the engineering team uses Slack.

We use Microsoft Copilot alongside Microsoft Office, integrating different AI engines according to customer choices.

The user interface needs improvement in terms of visual appeal and customization. The search feature could also be enhanced for better efficiency. Rating the overall solution would be nine out of ten.

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.

The user interface is simple. It performs well. It is easy to use. Anyone can use the product.

The stability could be improved.

I have been using the solution for one year and two months.

I haven’t had any issues with the stability of the tool. I rate the stability eight out of ten.

The initial setup is simple. We have completely migrated to the AWS cloud.

I will recommend the tool to others. Overall, I rate the solution an eight out of ten.

I have worked with Jira for agile scrum projects. Jira is a good tool that helps you track and monitor all your stories, scrum updates, and Definition of Doneness (DoD). We can track everything we need to track and pull the reports from the Jira tool. Based on the team's activity, we can monitor, track, and update the tasks we have assigned through Jira. We also use Jira for sprint planning.

The most valuable feature of Jira is the reporting feature, which allows us to track our team's tasks. You can export and play around with the reports. In the defect tracking tool, you can pull the data and generate reports with a nice graph. It's very user-friendly. The solution's user interface is intuitive and easy to use.

Sometimes, Jira becomes slow when more people use it. Then, we have to close it and log in again. The solution's stability could be improved, and it could be made more robust.

I rate the solution’s stability a seven out of ten.

Around 2,000 users use Jira in our organization.

I rate the solution an eight out of ten for scalability.

The initial setup of the solution is very simple. You can install Jira as a standalone solution. Deploying the solution on the cloud is very, very easy, and then you can access it from anywhere on the cloud.

I have used Micro Focus Quality Center, which is purely a defect management tool. We can also use Jira as a defect management tool. When you compare both tools, Jira is now the best tool for defect management and running scrum projects. You can even expose the Jira APIs to do automation.

If you find a defect, you can automate the process of logging in to Jira and erasing the incident. When you find a defect while running JMeter scripts, you can take the APIs and automate it to save time. The automation process can be done through Jira because it exposes its APIs to third parties to integrate with other tools.

You can expose Jira APIs and integrate the solution with other tools. You can have your own dashboard using the APIs. I would recommend the solution to other users.

Overall, I rate the solution an eight out of ten.