Jira Reviews

One of the valuable features is traceability from requirements to test cases.

Traceability was not available before. This is a great advantage for audits

I would like to see test execution modules.

We have used this solution for three years.

We encountered only a few issues with stability.

We did not encounter any issues with scalability.

Technical support is good. We use Beecom as the provider.

QC was used here, but I do not know why they made the switch.

JIRA can be parametrized quite intensively. Once you understood how it works, it works well.

We started here with this product, after the decision was made.

Use Beecom as the provider.

The ability to keep stories, bugs and documentation in one application is a valuable feature, as is the ability to easily create swim lanes for organizing work.

As everything is within one application, it is easy to write end-of-sprint reports.

It worked fine for my requirements.

Stability: we encountered occasional timeouts.

I have used this product on and off for about seven years.

I did not encounter any deployment issues.

We encountered occasional timeouts.

I did not encounter any scalability issues.

I did not need to contact customer service.

I did not need to contact technical support.

I have not used any other solution, before this product.

The setup was very straightforward.

We have implemented this product in-house.

This product is easy to set-up. There are many add-on applications to assist you further to manage all requirements such as Confluence for document control, Capture for testing, etc.

We are using Jira for user requirements, our development, and for our agile and scrum requirements. We create scrum boards for our projects.

The most valuable feature of Jira is the project package for development.

I have been using Jira for approximately three years.

 JIRA is very stable.

Jira has the ability to expand it is scalable.

We have approximately 25 users using this solution in my organization.

The technical support has been very good.

The initial implementation of Jira is not difficult because the solution is on the cloud.

The price of the solution could be less expensive. We pay annually for the solution.

The solution is very good and there is not much to improve. This has been working well. Our teams have been happily using it.

I rate Jira an eight out of ten.

We primarily use the solution for customer service and managed services, and for all the workflows for the services. It's also a bit of a CRM. We use it largely for technical support.

The solution provides an integrated platform for customer service. It's good at organizing our technical support for clients.

The solution has been very stable overall. We haven't had any issues with performance.

The pricing is reasonable. It's not too expensive.

The UX and UI could be better. It's something they need to improve upon. It needs to be updated and made more modern.

It would be ideal if the solution could be available as a mobile application.

We would like the solution to be a little less costly, although, overall, the price isn't bad.

I've been using the solution for five years or so. We've been using it for a while at this point.

I've found the stability to be very good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable and the performance has been good.

We've never reached out to technical support for help in the past. I wouldn't be able to speak to the level of service they provide.

We did not previously use another solution. We do not want to switch to something new at this time either.

Unfortunately, I was not a part of the company when it was originally set up. I have no idea how the implementation went. I wouldn't be able to comment on if it was easy or difficult and/or how long it took to deploy.

While, of course, in general, we always want the pricing to be lower, it's pretty reasonable. The costs aren't too bad.

We are just a JIRA customer and an end-user.

We are using the latest version of the solution. I'm not exactly sure of the version number.

We do not plan to switch to another solution. We're quite happy with this product overall.

I would rate the solution at an eight out of ten.

We use this solution for product development and issue tracking.

This solution provides us with a centralized view of issues, simple time registration, and excellent integration to Bitbucket.

The most valuable feature of this solution is the source linking on the commit level to git.

The speed of this solution needs to be improved.

Backlog pruning and visualization are poor. 

Uupdate:

Speed has improved slightly in backlog view with Jira 8.0, but there is still room for speed improvements.

It's difficult to group and manage the backlog and priorities on multiple simultaneous epics to get clear overview of how the backlog reflects a planned roadmap. (perhaps due to the fact that we have too many issues in the backlog)

It's really for Agile projects with storyboards, and then defect management.

The performance has been okay.

It has improved the Agile process in our company.

A lot of people in the business work with this tool so when you are searching for a new employee you don't need to train them on this tool. 

The reporting and the view, from a story to a defect, should be improved in the next releases. For example, how many boxes are assigned to one story, or how many tests are run on one story, and so on. This is what I miss in the tool at the moment.

The stability is very good.

We are about 700 - 800, and it works. Not all use JIRA but in IT we are 100 people.

I have not personally been in touch with support, but I think the support is very good. I haven't heard anything wrong with it.

We have two organizations. One is development, and they work JIRA. And the other is the business, which is responsible for testing. At the moment, we are going in the direction of DevOps and more Agile, and we would like to merge our tools together.

The important criteria when selecting a vendor, in my opinion, are that the vendor should be flexible, cheap, and the support should be excellent.

I rate it an eight out of 10. It's easy to use. People can become productive with this tool in a short time, and it is really the right solution for an Agile environment.

A lot of solutions show very well on paper. When you are selecting a solution, do a proof of concept in the environment.

We run pilots and product development using this for Agile and Scrum applications, in mechatronic product development.

It has performed well so far. We like it, we would like to expand it.

It's a tool that won't change the way that you work, but it supports the way that you work. Agile is changing your teams, changing your organization, the way that you work, and then JIRA will help you doing that across multiple locations, for instance. 

We don't do physical boards. I run a team with four locations, in three time zones. I need to work with online tools, and this is where the tool helps me. It helps me to use virtual Scrum boards across four locations, three time zones, and to plan my work.

The most valuable features are 

• the easy handling
• drag and drop
• what you see is what you get.

It's, smooth, accessible. It fully supports the Scrum approach, and the Agile way of working, and it has Agile thinking behind it, so this is very much helpful.

I struggle with Epics, how they are implemented in JIRA, because they don't work like any other Story, in a good way. I see a list of Epics, but although I can order them, there are some mismatches with how the Epics are used compared to what Scrum expects, or what Story mapping expects an Epic to be. 

For instance, if I rate an Epic, the Story points, and I rate the related user Stories, the Story points, they all count together. They're all summed up together. So, the overall Story points for the Epic, including the Stories, is double of the Story points. It just doesn't make sense. Maybe I'm doing something wrong, but I had to delete all my Story points on the Epics because they were counted including the Story points. This is not correct, and I would immediately improve that. 

I would like to see visualization of release planning. I can list the releases and I can give dates to releases, but to show how they are happening on a timeline, I would need to order the Portfolio part. But just for this, it may be too much to use the Portfolio for that.

The stability of the solution has been near perfect. I haven't faced yet any technical interruptions. 

There was one issue we had, technically, when we added 30 more users. The server hung. I don't know whether it was because of the tool, or what the reason was.

Scalability, I can't really touch yet. We have small scale approaches. We are about to scale. I think the idea about how to scale is not yet clear. It works perfectly for a team, that is pretty clear. How you do this for more teams, I haven't investigated this too much. Maybe the tool contains this, but currently it's not fully clear to me.

We switched because the visualization is a great help. So, really to transfer from a physical Scrum board to a virtual Scrum board implemented in JIRA, as well as so teams can work with us, and collaborate with us, on a Story to produce a result. Recently we tried to work with PDC task management. As a team, we had to learn it. It's possible as well, but not as easy and flexible as JIRA.

I'm not the selector of the vendor, but from what I can tell, from what our IT selects, the vendor should be 

• available for global support, should be accessible in 24 hours, if there's a larger issue
• able to collaborate with large enterprises, which sometimes have different cultures, different languages
• able to integrate into the existing work environment - we have this tool, and that tool; the tool should fit into our tool landscape
• able to provide training.

I would rate JIRA a nine out of 10. It's not a 10 because it's inconsistent, sometimes, in how it acts and reacts, like my example with the Epics. But it's a high rating because it's user friendly, it's easy to use, you do not need much training on it. If you know how to work with Scrum, you can easily use it for your own work in a small team. For multiple teams, I'm not sure. I can't judge this because I haven't done this yet.

We are using it for project management. We have cloud and on-premises deployments of this solution, and we are currently using its latest version.

It is very straightforward and easy to use.

It should be less expensive.

I have been using this solution for about five years.

It is scalable. We have about 500 users.

I don't have any experience with their technical support.

It is easy to install. It takes one to two days.

Our team handles its deployment and maintenance. We have a team of three people to manage it.

Its price is fine, but we would like it to be less expensive. We are paying on a yearly basis.

We didn't evaluate other products.

I would 100% recommend this solution to others. We plan to keep using it.

I would rate Jira a nine out of ten.