Jira Reviews

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.

I use the solution in my company as an ITSM tool. Our company's service desk and those working with the engineering team use the tool.

The integration between Confluence and Jira, along with Jira's ticketing system, is a valuable feature the product offers its users.

I opted for Jira since it was offering ITIL V4, and there seems to be a compatibility between ITIL V3 and ITIL V4.

From an improvement perspective, it would be better if Jira could offer more in the area of data analytics similar to what Power BI and Qlik offer to users. The tool currently lacks in the area of data analytics.

Jira needs to consider lowering its prices considering the competition in the market.

I have noticed a problem with Jira in the Philippines. In the Philippines, there are only a few companies that offer local support, which is alarming. In my previous company, when we requested support, basic support was not provided, and we had to schedule and deal with everything on our own.

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

It is a stable solution.

It is a pretty much scalable solution.

The solution's technical support is good. I rate the support a nine out of ten.

Positive

I have experience with ManageEngine and ServiceNow. If I need to deal with a project involving retail business, then Jira would be a poor choice because dealing with a retail business requires a tool to have an approach different from what Jira offers. Compared to ServiceNow, Jira is a bit better.

The product's initial setup phase was straightforward.

The solution is deployed on the cloud.

The solution can be configured within a week or so. If there are changes to be made in the solution, then it requires more time to configure it.

If I compare Jira's licensing model with that of other products, I think that the other products have a much better licensing model. Considering what is happening in the market presently, and as people are moving away from Jira and ServiceNow, more and more people have started embracing cheaper products in the market. I rate the product's price a four on a scale of one to ten, where one is cheap, and ten is expensive.

It is important to know that my company uses the free version of the solution since we are not a big organization. My company is currently looking into the configurations and other areas before going for the paid version of the solution.

Performance-wise, Jira is a good solution, but the problem lies in the part of its licensing area.

I rate the product's price an eight out of ten.

We use it for project tracking. We do software development. We implement software development lifecycle, and we use Bitbucket for CI/CD pipelines.

We have a lot of vendors operating on multiple projects, so in terms of operations, we need to maintain the backlogs of different projects. The sprint approach for roadmaps is cool in Jira, but we are looking at whether the same option is available in Azure DevOps because one of our clients is looking into using Azure DevOps.

Jira has a good reporting system. It also has an API, so we can do all sorts of reporting. 

There are a lot of things. A lot of features, such as time tracking, are only available through the marketplace. If multiple users are working on a user story, we aren't able to pull out the reports. So, there are many things that they aren't offering. They are available only through the marketplace. That's not good for a product.

I've been using this solution for five years.

It's stable. The stability on the cloud is 99%, but we have deployed it on a virtual machine. 

Both cloud and on-prem deployments are scalable. I'd rate it an eight out of ten in terms of scalability. 

Our clients are small and medium enterprises.

I'd rate it a nine out of ten.

Positive

The setup on the cloud is easy. I'd rate it a nine out of ten in terms of the ease of setup. The on-prem setup requires some work. I'd rate the on-prem setup a five out of ten in terms of the ease of setup.

We have four people who are working on Jira maintenance.

It's not very cheap. It's also not very costly. I'd rate it a five out of ten in terms of pricing.

I'd recommend it to others. Overall, I'd rate it an eight out of ten.

I use Jira for project management. I track all my projects through Jira, including the resources, the time, the deadlines, or the roadmap. For me, it's the tool to check the status of the project. If we have time to get more people on the team, we can use it to show the up-skilling and the availability of the team.

They offer 24/7 support.

It's easy to set up.

There's lots of documentation to help you learn about the solution and troubleshoot issues.

The stability has been great.

A company can scale Jira if it needs to. 

It includes by default all the necessary tools for a project manager to work and make their work more efficient.

The reporting tool and the approval tool need work. The basic reporting tool includes only a few basic reports. If you need an advanced report you need to download a specific plugin, install it, and customize your reports on it. Sometimes you need to know SQL, let's say, in order to get the reports. It's not user-friendly.

With the approval tool, it's complicated in order to create the flow in Jira in order to achieve the approval process among different people. That needs to be simplified.

I've been using Jira for almost now seven years. I have used Jira from 2015 until now.

It's a very stable solution; we've had no problems at all with that. There are no bugs or glitches. It doesn't crash. It's reliable. 

The product is quite scalable. If you want to expand it, you can. 

We have hundreds of people on the solution in our company currently.

I've used customer support in the past and have found them to be helpful and responsive. 

Positive

The initial setup is not complex. From what I understand, it's an easy setup and it's straightforward. They have a lot of user manuals as well, and they have also 24/7 support across different countries if you need help at any time.

While there is a cost associated with the solution, and licensing needed, it's not an aspect I deal with directly. 

I'm not sure which version I am currently using. the admin team handles the versions and updates. 

I'd advise new users to read the user manual first, before jumping in. They are really helpful and informative. 

I would rate the solution at a nine out of ten. It is one of the best tools that I have used. It's helped me a lot in my daily job. For me, it's the best tool in order to track teams and projects. 

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.