Jira Reviews

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.

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.

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. 

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. 

I've been using this solution for 10 years. 

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. 

We use the solution primarily for project management. We organize our work by projects with epics, et cetera. Below that, I believe we are using a Zephyr plugin for QA. We don't use it for product planning.

I would say it's a necessary evil to use a product such as Jira. All of these solutions are a necessary evil. They all have their pros and cons.

For what the solution does, it's fine.

The solution offers a lot of plugins.

The solution is very configurable.

There's a bit of a learning curve, which I'm not a huge fan of. It's not exactly user-friendly per se.

I would prefer it if the solution was more intuitive.

There are just so many options, that it's pretty overwhelming as a product. There's too much to focus on.

We do find that we need plugins and have created integrations with more robust analytic solutions than Jira provides.

Personally, I'd like it if there was more flexibility in how you could manage the backlog at a project level.

I've been using Jira for about six months. It hasn't even been a year yet. The solution is still very new to me and I am still learning.

The solution is very, very stable. There's no problem in that sense. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

You can easily scale this solution. If you need to grow it out to meet your company's needs, you can do so. That's not a problem.

We have about 300 users on the solution right now. They include developers, administrators, senior leadership, analysts, designers, and project managers.

I haven't used technical support at all. I can't speak to their reliability or level of knowledge.

Although I wasn't hired at the outset of the company, it's my understanding that they've always used Jira as a solution.

I wasn't involved in the initial implementation of the solution. I just started working with the company six months ago. Honestly, I'm still learning the solution.

I don't have an opinion on the pricing or licensing. It's not really a main concern of mine. I don't have access to any information about what the company pays.

We're just customers. My company doesn't have a professional relationship with Jira.

I'm not sure which version of the solution we're using. I'm not sure of the last time we updated the solution. I've only been at the company for six months.

I'd advise other companies to dedicate two full-time people to learn the solution and train other team members. It's a big learning curve for users. It takes time to get into it. Having dedicated trainers would help onboard people.

Overall, I'd rate the solution seven out of ten. If it was more intuitive, and there was less of a learning curve for new users, I'd rate it much higher.

The configurable workflows and boards make it easy for us to execute and oversee our own unique process. The portfolio feature allows you to conceptualize your roadmap and experiment with various scenarios before committing to execute. Once you learn how to configure the system, it is extremely powerful.

JIRA has created visibility for our IT organization that did not previously exist.

There are some minor quirks, such as zero-point stories not appearing in the portfolio scope. We often poke stories at zero points because we have a very small group that needs outside help from time-to-time. We need to track these stories without impacting team velocity, so we poke them at zero.

These stories will not appear in the scope/schedule in the portfolio because the system interprets zero points as zero scope, even though the issues are open, assigned to the release and assigned to a Sprint. It would be nice to be able to see them in the schedule.

We have been using this product for three years.

We did not encounter any issues with stability.

We did not encounter any issues with scalability.

I would give technical support a rating of 5/10. I have only asked two questions in the support forums. One was answered very quickly and the other was never answered.

I previously used CA Agile (a.k.a. ‘Rally’). My company decided to switch to JIRA because we were already using it for bug tracking. Once the Agile/Portfolio features were released, we decided to use JIRA for all IT project planning and tracking.

The initial setup was pretty straightforward. One thing I personally don’t like is how the system, by default, assumes that all projects will have a different workflow and screen configuration. This adds complexity in my opinion. It should assume that there is a default workflow and configuration across projects and then allow you to copy and customize the defaults.

It is very cheap if you forego the local instance and stick to the cloud.

We evaluated Microsoft TFS and Targetprocess. Neither had a Portfolio planning feature, which is why we decided to stick with JIRA.

Establish a basic project management methodology and workflow first, with clear roles and responsibilities, and then use this product to execute. It is only as effective as you are disciplined in your sprint planning and execution.

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.

My company uses the product for the user storage it provides. The tool is also useful for requirements management and test management processes. The product is also useful to track the hours people in the company have spent on testing and test logging.

The solution's most valuable features revolve around the dashboard view, which has a burndown chart indicating progress. I also like the tool's ability to provide details phase-wise, allowing users to see how many tickets are in development and how many are in the testing process. It also helps users see how many tickets are ready to move to the production phase. The aforementioned areas of the tool are pretty frequently used.

Some of the customizations are definitely a little challenging. I depend on Zephyr to manage certain reporting aspects and deal with the challenges of customization. More than a thousand records are something that our company cannot retrieve, but with the administrator's permission, the limit can be increased. Some of the functionalities to increase the limit of retrieval, in case there are more than a thousand records, could have been included as a default feature since it would be helpful if I wanted to do some analysis or if I wanted to extract all the details when my limit is only a thousand records and then I have to search for another way to find and extract the details. If the aforementioned details of the issues in the product are addressed, then it would be great.

If there is a provision to increase the number of records retrieved, it would be really helpful. In the tool, only a predefined reporting is there, and it helps with some of the more customized reporting, like Power BI Report Builder, so the area of reporting can be enhanced and it can be really helpful.

I have been using Jira for two years. I am a user of the tool.

Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution a nine out of ten. The product is always up and running in my company, and we have not experienced too much downtime in Jira, making it a very efficient tool.

More than 50 people use the product in my company.

I haven't had the opportunity to interact much with the product's technical support, but based on the inputs from the other members of my team, I can say that my company was able to get support from Jira whenever required. I rate the technical support a nine out of ten.

Positive

The product's initial setup phase was not very complex, as it is manageable.

The solution is deployed on the cloud.

Compared with Jira, I feel Microsoft ActiveX Data Objects (ADO) is coming up pretty fast in the market since the features attached to the paid version work well. Microsoft ActiveX Data Objects (ADO) can easily integrate with other Microsoft products without needing any customization. Microsoft ActiveX Data Objects (ADO) is growing pretty fast in the market.

My company uses the product for planning tasks.

The product has played a major role in helping my company in the area of bug tracking. During the testing phases, be it SIT or UAT testing, if there were any issues, our company used to log the bug using Jira, and then we connect with the respective users, so we have a track of which particular bug and check to see if the bug is related to which user storage.

Jira helped our company's project management, analytics, and reporting parts. If you look at the analytical part, my company used to get the hours we have availed each of the user storage. When it comes to the user storage part, my company would like to see whether the hours we consumed were optimal or if it was over-consumed, which is information that we track with Jira. The tool is useful for tracking progress and seeing where my company stands when it comes to tickets. Each ticket might have a certain due date, which the company gets to see using Jira. Altogether, the tool helps users eventually understand the team's progress, the current sprint details, and how much of the team's capacity has been used. With Jira, my company gets to see the aforementioned details, so we were able to track it with the product's dashboard.

I am not used to using the product's integration capabilities with other solutions.

The product's user interface is good.

I recommend the product to others who plan to use it.

I rate the tool a nine out of ten.

We use it within our organization. 

It's to handle all the main technology projects. It's for managing mobile banking, internet banking, all the new products, and all technology-related projects.

We get the big picture of what is going on within a project.

The solution allows us to provide access also to the senior management, to see how things are progressing and to point out quickly what's going on, and help to focus energy on the things that are not going well.

The main benefit we got from the product is the consolidation. 

I like the roadmap or the new version with the roadmap that the solution offers. For us, the roadmap was a really great feature.

It's got very good portfolio management. 

The initial setup is easy.

The licensing is transparent. 

It's a stable solution.

Scaling the product wouldn't be difficult. 

Whether you are an expert in Agile or just it's the first time you are talking about it, it's a very user-friendly tool. It's a very simple tool. It's not complicated and even the integration and the usage is very simple. You don't need to be an expert. 

Whether you have small teams or big teams, it's the right tool.

We'd like to use it with non-Agile projects in the future, however, right now, it is a very Agile-focused product.

In general, however, as a solution, it's quite complete and I cannot speak to any missing features. 

I've been using the solution for one year now. 

At the moment, we have not had any issues with stability. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

At this time, we are not tackling scaling at the moment. The organization is not mature enough to scale up.

That said, based on the experience we have had now, if we want to scale up, it should not be that difficult.

We have approximately 200 people on the solution currently. Those users are mainly comprised of the software development teams plus some portfolio managers and program managers and the project managers as well.

We do plan to increase usage in the future. 

I have not had any interaction with them as we haven't had any major issues. We have a contract with the integrator, however. While everything is going well for the moment, we would have access to assistance if we needed it.

I've used Clarity, however, it was used in another organization.

The initial setup was not complex at all. It was very straightforward, very simple.

The full deployment took about three months.

We have four people capable of handling any management tasks related to Jira. 

We had the setup services handled by a reseller of Jira.

It was a very good experience. It was very fast compared to what we expected from the contract. It was a nice surprise.

We have yet to see an ROI as it's been just one year, including the three months of implementation. Maybe in the next six months, we can have visibility on that. For the moment, it's still in progress. We cannot say anything about any ROI.

We pay a yearly licensing fee for an enterprise-level license. 

It's quite similar to the pricing that they have on their website. It's quite transparent from their site. They have a package that charges per user, however, they have some scalable packages, for zero to 10 users, from 10 to 20, from 20 to 50, and so on. You can choose, depending on the size of your company or the number of users. The costs are quite transparent.

While everything is included in that package, the integration or the customization is a different fee. There's a project apart from the integrator, which may vary in cost.

We are just customers and end-users.

I'd rate the solution at a nine out of ten. There's always room for improvement, however, it's a very good solution.

I would recommend the solution to others.

I primarily use the solution for project management. 

The product is quite easy to use and simple to navigate.

The solution isn't too difficult to learn.

It's flexible and it can provide a lot of different options, such as dashboards, that you can create and manage. You can really tailor-make your own dashboard depending on your needs.  

It's quick and very stable. 

I don't see many issues while I'm using it.

You can basically communicate with all kinds of different teams that are using Jira and you can do that under the product, as a single platform.

Sometimes the solution doesn't communicate well with other platforms. It's quite difficult to integrate things and make the data flow from A to B, to Jira, and then back to other areas.

Nowadays, you see a lot of product management tools, like monday.com and they are very user-friendly. They offer features that allow for cosmetic changes, and you can actually change the color and the form to your own liking. ira is lacking some of that flexibility. It's not critical, however, for the wider user base, many would like to see that.

I've been using the solution for three years. It's been a while. 

Overall, the performance of the tool is quite reliable with few bugs or glitches, and it runs very fast in the browser It doesn't crash or freeze.

The solution can handle a lot of tickets. I've seen it handle more than 10,000 with no problem. It's almost unlimited in terms of scalability.

I'm a customer and an end-user.

I'm using the latest version of the solution right now. I cannot speak to the exact version number we are on currently.

I'd rate the solution at a nine out of ten. We've been very happy with its capabilities. 

I would recommend the solution, as it is quite powerful.

I'm overseeing the developments done in Jira. 

The thing that I do like about Jira is that it is relatively easy to understand. In some respects, you don't have to read a lot of ticket information, and you can start pulling down. Everybody is using it, and it works for a lot of people who are just doing enterprise development, cloud-based development, and things like that. It is built for the general audience. 

It is a good defect tracking tool. It has a lot of capabilities and functionalities. There are a lot of graphs and a lot of tracking. It can be sprint-driven if you want. There is a lot of data that you can pull out for estimations. It has got a lot of out-of-the-box functionalities that are kind of like the Jazz platform for out-of-the-box scrum and other such things. 

It also works well with all the integrated tools that you buy.

One thing that I don't like about Jira is that when you do an export, it only allows a thousand issues. So the export feature needs to be better. 

Another thing that I don't like about it is related to epics. There are times when you simultaneously want to have a story tied to two epics, one driving the content change and one driving the format of that evolution. It is not truly a parent-child relationship. It is a single-parent relationship to the stories. It would be nice if you had the capability to tie in multiple epics to a particular story. It is a rare case, but we have that. 

Setting up and executing a triage board should be simpler in the sense of how you do the admin. I come from a regulated space, and there should be easier control of who approves and reviews a system board to oversee all the defects. It should have easier out-of-the-box solutions to allow us to set up a triage board at the system level, the software board level that reports to the system board, or the test level that reports to the software board at the system level. There should be out-of-the-box solutions to migrate that and say that who are the three people on the triage board and if they have these admin privileges. Software review board and test review board would be another thing.

We have also had a problem with the integration with Bitbucket Pull Request data. It is an add-on to the tool, but it is not fully integrated. It is not easy from my perspective. Jira, Bitbucket, and Xray should be smoothly integrated. Xray is pretty good, but Bitbucket is standalone. So, when you pull out the data from a comma-separated value and want to move it into a new database, you have to reenter the data. You somehow lose that Pull Request capability. Pull Request through Bitbucket and the review of the code should be easier to manage. You could use a software package called Crucible to go ahead and mark how you did the review, who reviewed it, and who is the independent reviewer or subject matter expert, but that also should be easier to set up. If they want Jira to be the one-stop shop of the view of all of your deliverables, not just from a defect tracking perspective, but also from a requirement perspective, a code perspective, and a testing perspective, it needs to pull out more data and work better as an integration tool. 

I'm using Jira for the requirement repository. When I do requirements, it would be nice if I had the capability to say that for your requirement, I'm going to give you traceability to support a traceability report from Xray. I'm also going to give a requirement ID number in the ticket. You could use Jama and things like that, but it would be nice if Jira supported that.

We had on-prem and cloud deployments. We had to go to on-prem because of the security measures that were deployed. On-cloud didn't have the same capability. If you have one database on the cloud and the other one is on-prem, they don't talk to each other. It would be nice if you pulled it in and you could switch and say that I want to go on-prem because I got greater security risk.

When we go into the regulated space, I require a lot more integration and capability for tools. It is very hard to get tools to perform at that level because they're built for the general audience. In the regulated space, whether you're in medical devices, avionics, or any other regulated environment, tools have to be validated. I've worked with some companies in the past that had the capability to facilitate that validation. With one of the solutions, you could go ahead and buy a validated suite or a requirement package that will validate the tool for your use, but it is such a small market for Jira around the world that nobody really cares about that.

On their website, they show a bunch of tools that work with Jira, but it would be nice if they gave you examples and said that if you're a regulated medical device or regulated, here's a solution that could work for you. Here is Jira. Here is Crucible, and here is Xray, and here is what it'll do for you. They could also ask how do you do the requirement management? Do you use Jama that ties to Jira? It would be awesome if they had some use cases that showed people how to use Jira as the building block and how to add something on the front end for requirement management, and something on the backend for testing, such as Crucible for the peer reviews and Xray for the test management. People would see it and say that I want to do that.

It would also be nice if it could provide some lock-out capabilities based on your development and environment preferences. For example, you can specify that no one can close a defect until it has been tested, or until a particular task is complete, you can't go to the next phase. It would be cool if you could have something like this set up versus someone configuring it in the background.

They have got 10,000 licenses of Jira, and they have teams around the world deploying it across multiple geographies. All of that works fine.

I haven't used them because this company has its own tech support. So, I've been reaching out to them.

Most people who turn to Jira say that the return on investment is much better. 

Jira and its solution off the shelf are cheap. It is cheap for startups.

It depends on what you want to use Jira for, and what's the problem you're trying to solve. If you're going to do defect tracking and management of an artifact and you have got requirements, code, and tests, and they all got to summarize, you have to then go ahead and take Jira. You can then buy Crucible for the peer reviews and Xray for the test management and get them to work seamlessly with each other. 

I would rate Jira an eight out of ten. It is fairly cheap. For a nine or ten, it would be like DOORS and Jazz platform, but the problem with that is that it would become really expensive.