Jira Reviews

We are using it for software development tracking, bug tracking, feature tracking, and so on. 

We are using the cloud version from Atlassian, and we have its latest version.

The way we can define and customize the search queries for the tickets in Jira is most valuable.

The way to configure it can definitely be improved. It is very difficult and complex to configure. Its configuration should be simplified.

I don't have any requirements for new features. It is a standard system, and we use just a part of the functionality.

I have been using this solution for five to ten years. I use it on a daily basis.

Its stability is good. In the last five years, I haven't seen any outages. 

We are a very small team, and we don't have any requirements for scalability.

I have not contacted their technical support.

The initial setup and the out-of-box features and functions are very straightforward. I would rate it a five out of five in terms of ease. You can just create an account and start to use it. 

It is a cloud solution offered by Atlassian. There is no on-premises setup, and it doesn't require any maintenance from our side.

It is subscription-based, and we probably pay yearly. I would rate it a four out of five in terms of price.

I would rate Jira an eight out of ten.

The design of the interface is clean and not too busy visually.

I'm really new to Jira and I haven't used all of the features. However, it is quite difficult to use and manipulate. It was a little complicated for me and I don't know if it's difficult globally for others, but I had a difficult time understanding it at first. I used it for issues,  epics, stories, tasks, and sub-tasks. For first-time users, Jira could be made better to help them understand.

When you want to create something in Jira, whether it's a story or an epic on a task, you have to create a thing called an issue, and inside the issue, you have to put what type of issue it is. Either it's an epic or a story. The fact that it's called an "issue" was a little confusing for me because I didn't know where to search when I wanted to look for tasks and stories. I didn't know that I needed to search for issues and not only tasks or topics.  

I have been using Jira for approximately one month.

Jira has been a stable solution.

I have found Jira to be scalable.

We have 20 people in my company using Jira.

The setup of Jira was simple.

I did not compare Jira to other solutions.

I have not had a lot of time to explore the solution. My rating might be higher if I had used it more.

I rate Jira a three out of five.

We are using Jira for the internal project and issue management or tracking.

The most valuable feature of Jira is the integration with all the different Atlassian tools. They all integrate very easily.

Atlassian has multiple tools and it becomes difficult for a customer to process everything differently. Atlassian should combine them and form a single solution for DevOps by including the Jira Confluence, Bitbucket, Bamboo, and others. This would be much easier for customers by purchasing a package, rather than purchasing bits and pieces. With Azure DevOps and other companies, it becomes easier to go with one company having multiple areas that they can cater to, but in Atlassian, the problem is that you have to select different solutions to have a full package. For example, to have document management customers have to purchase Confluence and for Git repository management they have to purchase Bitbucket, et cetera. There is always another add-on that you need to attach to have a complete solution in Jira.

I have been using Jira for more than five years.

I have found Jira to be stable.

Jira is a scalable solution.

I did not have any issue with the use of technical support from Jira.

The initial setup was easy.

I would advise others that Jira is a good solution and I would recommend it.

I rate Jira a nine out of ten.

Its use case just depends on the company I've been with at the time. I have used it for defect management, development processes, and status. At one point, we ran our entire risk platform out of it as well.

The dynamic communication and the ability to customize it the way we want are the most valuable features.

Its ability to perform true executive-level status reporting could be improved. There are a lot of benefits there, but there are also a lot of things they can and should expand upon.

I have been using this solution for about eight years.

I have not interacted with them. I've struggled with getting Atlassian resources, but that could partially be my fault.

It depends on the type of license. In terms of subscription, it is cheap, and it works pretty well.

You need to investigate and understand dynamically what it is that you're looking to do. Don't just dive in and start creating. Before going into it, you should really organize your formatting or direction of the cause. There are other tools that are like cookie-cutters. Jira is so customizable that you really need to define what you're going to do with it.

I would rate it a nine out of ten.

We are using Jira for our test management. We're using it to record our inspecting results and to regulate the evidence in the report. 

The integration could be better in Jira.

I have been using Jira for approximately 15 years.

I have found Jira to be stable.

Jira has been scalable.

There is an annual subscription to use Jira.

I would recommend the solution to others. I have been happy with Jira.

I rate Jira a seven out of ten.

We use Jira mostly for task coordination and assignment. Additionally, scrum methodologies defined work items and bug issues. If we create any bugs all of them are fixed.

Jira can improve by making methodologies better, such as scrum and agile. Additionally, improvements in Kanban boards are needed.

I have been using Jira for approximately five years.

The stability of Jira is good.

Jira is scalable, this is in part because in our company we use it on the cloud.

We have not needed to use the support from Jira. It is easy to find information on Google or any other search platform. If we encounter an issue we can find the solution online.

The initial setup of Jira was simple.

The standard package of Jira is for 100 users. They should offer more packages for other increments, such as 500 or 2,000. In my previous company, there was a free package that provided a minimal number of users.

I rate Jira an eight out of ten.

It's scalable.

It's easy to deploy.

The cost of the solution seems to be reasonable. 

Once the solution is deployed, it's not easy to configure. If you have a lot of capability, it's very dynamic from the back end. Therefore, when setting up the workflows, it can be a little bit complex. We did a lot of functions on managing the development and that's why maybe it's a little bit complex. Basically, in order to design a workflow in Jira, it's not a straightforward task.

From a feature perspective, not much is missing. However, they need to put some investment into the user experience. It needs to be easier to use, more friendly, especially on the configuration part. It's a hassle. You need to deal with a high learning curve in order to understand how it's configured and how it can work.

We've used the solution for more than eight years now.

The solution is scalable. 

We have more than 50 people using Jira at this time. 

We do plan to increase usage. We are growing. Since we are growing, we are increasing Jira as each member on the technology team needs an account for development, business analysis, or testing.

While the initial setup is pretty simple and straightforward, handling the configurations and the workflows can be complex. 

I didn't attend this in the development phase. In testing, I did the same effort and it took me a month to set up while I was deploying a test stream. I worked on the testing workflow as well, the defect workflow. That said, I don't know how long it takes for them to configure Jira.

We handled the setup in-house.

The licensing is per unit. My understanding is that it is pretty affordable. However, I don't directly deal with licensing.

We are just a customer and an end-user.

From a testing point of view, I would rate it at a six out of ten. I use it as a defect management tool, and it, for me, it's not easy to use.

We are using Jira for task management.

The solution has helped our organization be organized. We are able to create sprints in Jira to manage projects and tasks according to capacity and time.

Jira can track projects, time management of assignments, and keep everything on schedule. The performance of the solution is good.

Jira could improve by making the user interface easier to use and the functionality could be better. While we are managing multiple sprints and other elements of the projects, it's very difficult to manage the labels and other aspects.

I have been using Jira for approximately two years.

The stability of Jira is good.

We never faced any kind of issue in the scalability of Jira.

In my department, we have approximately 200 people using the solution. There could be more people using the solution in my organization but I am not aware.

I use Jira every day.

I have contacted the support from Jira a few times. They have been good in my experience.

I have not used another solution previously.

The implementation difficulty of Jira depends on what tools you need. In the company I am working for, it was not difficult because we have a small team and we were not using many tools.

I would recommend this solution to others if they cannot find a better one.

If someone wants to implement Jira, then it should be fully transitioned. In the beginning for us, it was not implemented one hundred percent, which caused some hassles for the transition for everyone.

We have benefited from the use of Jira has improved the way we operate. You can see what everyone is doing in your team and you can check and get updates on progress.

I rate Jira a seven out of ten.