Jira Reviews

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.

Public Cloud

We use it for IT project management. We manage the timelines and resources, mainly people resources.

It is a stable solution, and we have had no issues with stability.

For our company, we're thinking about not only project management solutions but also collaboration solutions, and maybe if Jira had a chart or quick commenting option, it would be great.

I've been working with it for two years. It is a cloud-based solution.

We have had no issues with stability.

We currently have ten users, and it is free for ten users. However, we hope to increase usage.

I would rate Jira at eight on a scale from one to ten.

Our testers and QA teams use this tool. 

This solution is easy to use and takes a lot of burden off the QA team.

I'd like to see a more stable product with more integrations, as new products are coming on the market daily.

.

The technical support could be better, a little more customer friendly and knowledgeable.

The initial setup was quite straightforward. We had our technical team deal with it. We currently have around 25 people using the product. 

We pay an annual licensing fee. 

I rate this solution an eight out of 10. 

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)

We have been using this solution for seven years.

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.

- Jira is used for bug tracking, issue tracking, and project management. - Jira has a powerful API, which means you can easily import or mash up your data with another system if need be – you haven’t locked yourself in! - Jira has been designed with a focus on task achievement, is instantly usable, and is flexible to work with. -you can create individual issue level security schemes, and specify the visibility of comments and work logs.

-At first, the documentation is typically light on needed information, is buggy, or is a little old. In general I found that I needed to do a bit of searching between the Jira documentation, issue tracking system, and the forums in order to get the information I needed, and it still didn't answer all of my questions. For the rest, I took a look at existing plug-ins to see how they had solved the problems. -I have found that Jira's customization can be very confusing in terms of configs and work flows, issue types, custom fields, etc. One should be confident and willing to do a lot of homework when taking on the implementation of anything other than the out-of-the-box functionality.

Jira is a bug and issue tracker primarily intended for software development. We use Jira internally to track all engagements within our team; as well as track bugs and issues for the web apps we develop. Jira is a very customizable product. It has a built in field builder that essentially lets you choose what fields you want to capture for your project. You can configure Jira’s custom fields at a system-wide, project specific and/or issue type level. Jira’s reporting component (or ‘filters’) make it easy to extract the information you want out of the system in several formats. Finally, Jira’s workflow features make it easy to define screens, based on business processes you might have.

It is easy to assign books, story styles, move across platforms and to different stakeholders while using this platform.

It has an easy UI that can easily plug-in to every level.

The CACD solutions on JIRA has some plugins, but they are not easily understandable or workable. 

More than five years.

It is definitely a stable product.

The scalability is fine.  

Tech support is good. 

We had a JIRA administrator help us with the setup, as well as an administration team. It took a bit of time to integrate the JIRA to our system.

In comparison to other solutions on the market, it is cost-effective. 

We looked at Micro Focus ALM vs JIRA, but it was quite expensive in comparison.

It is a user-friendly solution that is simple to use.