Jira Reviews

We use Jira for multiple uses; project management, task management, and we are starting to use it for release management.

The feature that I have found most valuable is its ease of use. I don't need to train anyone to use it, I just give them access and they can use it to add comments, move their issues, change the status, monitor, read, and so on. For these results, it is very helpful. I also like the customization that we had for the workflows for the different issues, it's quick and easy to customize. The reporting is also easy and the dashboards that they provide are really helpful and simple. It does not need a lot of experience with reporting and presentation to get to what you need. Also, most of the advanced reports that you need to create can be exported as Excel files.

I have been watching an issue develop. There is a difference between their cloud and their  server versions. The next-gen project, which is an advanced feature that allows you to visualize the road map of your delivery over multiple products and over time, is not available yet for the sever version. It appears there in the list, but it's still not right. I've tried to use it many times and I am watching the device show their tracker, but it seems they intentionally want this to increase the utilization of the cloud instead of the server. It is really a nice feature and it's a shame that we don't have it.

Additionally, it would be really nice if they added some custom reports so that you could build your own report through any open source or commercial plug-in like Crystal Reports. That would be much easier for them to accelerate. You can create a report template and use it frequently.

There are a few features I would like to see in the next release. For example, the layouts could be easier to configure on the screens. I know it's easy to customize. For each issue type you can create and modify your screen. But it would be easier if you could enlarge, copy, clone, and visualize them in a model in a visual way. It's really hard for me as an admin to compare different screens or even to copy one screen with one additional field. I believe that is creating a lot of confusion for end-users because usually admins are looking at each field independently, where it's located, in which position, and which screen. So that all needs to be improved from an administration point of view to make it easier to visualize and compare between the screens.

I have been using Jira for almost a year now.

In terms of stability, it is fine.

The initial setup is easy and straightforward. The deployment is very easy. It just took one server.

It took one day to set up the database and then start the configuration. That is straightforward. And I believe they have a newer deployment model that they can deploy on Docker and other container platforms.

I did it myself with some help from other team members.

Jira is an amazing tool, but to get the process streamlined is a challenge. So don't start from Jira. Start with your process first. Agree on the workflow, identify all the stakeholders, and then from there you can go ahead with Jira and implement anything.

On a scale of one to ten, I give Jira a 10.

Everything already provided is perfect. We are using Jira perfectly for one year now and it's absolutely great.

The primary use case is for software development teams to manage their work.

The most valuable features of this solution are workflow and reporting.

The team construct could be simplified. We use Jira with Tempo Planner, and Portfolio for Jira, and at times it is not always clear. With Portfolio, it's the same as Jira but with Tempo, it clashes. It's not a seamless transaction.

We would like to see integration between Tempo and Jira. For example, if I create a team in Tempo, I would like to be able to use it and re-use it Jira as well. 

In Tempo, if you create a team then you are able to link that to a project in Jira. I would like to have that same capability, where I can link to Portfolio for Jira. Specifically, if I create a team in Tempo then I want it available in Portfolio. When I am planning the work for my team, it would be easier to have that capability available.

I have been using Jira for approximately four years.

It's a stable solution and we have not had any issues.

Jira is scalable. 

We have more than 13,000 users and we have not experienced any issues with the performance or scalability. We are able to scale pretty well. 

I work with Jira on a daily basis, as well as offer support to users and guide them into making the best use of it.

We have a relationship with Atlassian. I have not personally had to contact technical support, but I do know that we have a technical account manager to whom we report any issues.

My advice for anybody who is implementing Jira is that it easy to use but you want to understand what your requirements are. You want to know what you want to use it for, and what you want to achieve by using it. 

With Jira, you get what you input, in terms of your data. For me, I get what I need out of it.

I would rate this solution a ten out of ten.

The solution's most valuable aspect is its workflow sensibility.

The user and group management could be improved in a big way. There really are a lot of administrative areas that require a lot of screens which could be improved in many ways.

A lot of the user interface could be updated.

Technical support is lackluster. It could be improved.

They need to address a lot of the requests that people have had over the last 10 years. Instead, they rely on third-party tools to provide these features. They don't seem to understand what it is their clients really need and instead just assume a plug-in can be made for whatever the purpose is.

I've been using Jira for ten years. It's been a decade now since I first started working on the system.

The solution is extremely stable. There aren't bugs and glitches. It doesn't crash or freeze. It's quite reliable.

The solution is absolutely scalable. If an organization needs to scale up, they can do so easily.

Technical support is pretty bad. They rely on partner companies for support and don't really have any of their own internal teams that can help.

The initial setup is not straightforward. It's quite complex. However, you do tend to get used to the process after a while.

The solution is quite expensive. I'm not sure of the exact pricing, however, I know it's not cheap.

We're an Atlassian partner.

I'm actually using various versions of the solution. I stick with versions seven and eight, mostly.

I'd rate the solution seven out of ten.

We use it to trace our business needs development.

We have some nice dashboards out there where we can track needs for clients or track internal projects.

This is our way of communicating with different teams. We are a global company. I am based in San Diego, for example. A lot of the BAs are based in Paris. The development team is based in Minsk. We absolutely need to be in constant communication and on the same page.

With the time differences that we all have, it is very hard to kind of get on a call and centralize the information in person or during meetings. This solution makes it possible. 

One of the most valuable aspects of the solution is the fact that everything is traced on one ticket on Jira. We know exactly what has been done and what is left and we share the same feasibility we are assigned. We don't have to wait for team updates or emails or calls or even reminders. We just need to look at the same ticket and we know in real-time exactly what is happening. Without Jira, I don't see how we would be able to manage and trace in a very consistent, effective way.  At least, not across all of our development initiatives.

I have never been trained on Jira, to be honest. However, it's easy to navigate. Even for somebody who is never on it, it's very simple to pick up and understand. The only caveat is that when you get a bit more in detail, or you have some business requirements, you don't have documentation that you can just go and consult to enrich your portal or access.

One aspect of Jira that is very nice is that we are able to integrate other tools that our company is using. For example, we do use Salesforce for our support team and that's linked to Jira. Slack, as well, is also integrated into the system. It makes everything so much easier.

Jira has recently updated their UI, but more can be done to make it even better.

One thing that is missing is notifications that we can send out in an automated fashion so that we don't have to log into Jira every single time. We do have dashboards on our navigation pages, but we need to log in to see the current status. I can't just click reports every once in a while to trace or track projects, I have to log in to see. I'd prefer it if the data automatically came to me instead of having to go seek it out. 

It's possible the dashboards and the reports are something that can be properly configured on our end. However, I'm not the Jira administrator in our company. I probably just don't know how to do it. Jira may actually be able to trigger these kinds of reports. However, if they don't have this functionality, it should definitely be added.

 I have been using the solution for four years now.

We've never experienced any downtime with the app. I can't recall any bugs or glitches. There haven't been any crashes of any sort. It's very reliable.

I would say the solution is pretty scalable. Every single project team in our company uses it. Our staff, our BA, our developers. We do also have DevOps teams using it. Everyone uses it for different purposes. Our company, over the past ten years, grew exponentially. We've tripled our size and we never had any downtime with Jira. 

We have business owners, developers, quality testers, business analysts etc. on Jira. We have internal consultants from professional services teams, who trace the needs as well so that they can transmit information to their clients. All the top management personnel go to Jira to consult the dashboards as well. If they wish to trace the progress that their teams are making, they can do so. The solution is basically used in every aspect of the company, and as the company grows, so does the usage.

I've never had to reach out to technical support, so I can't speak to how they are.

When I joined the company, we already had Jira. 

I wouldn't consider it complex at all.

I wasn't here at the initial setup of Jira, however, in our company, we have a Jira administrator. Whenever we have a project to review and need to know how it's laid out and how we can place them better, etc, it goes through this person. She analyzes the needs and does it for us. 

 She knows the tool pretty extensively, but we don't rely on external consultants to do it. We have somebody from our company who does it for us and acts as our own Jira professional. They would be the one that basically helps you with the setup for your project needs.

I don't handle the finance side of our relationship with Jira.

As far as I know, no other solutions have been considered as we've been pretty satisfied with this tool. 

I'd advise other companies to go for it and try using it. Jira is one of the biggest players in the market. It's a scalable solution and very user-friendly. The onboarding is quite simple. I have never been trained and I've been using it for the four past years. Whenever there is a new release on Jira, we get a guide, which is helpful, and instructions as we use the latest version that comes in the form of pop-ups on your screen. If you want, you can just disregard it, but once you discover them, you can just hover over with your mouse and you can see the new features. If an organization is looking for something that will be easy for its workforce to adapt to, Jira would be a smart choice.

With the communication and the bridges that we've established with other tools, it's helping other teams get the information they need without having to get the Jira license or get them to go onto Jira. They just need to find their tool and they get the update from Jira in real-time.

We use JIRA for software development projects and the implementation of business workflows. Our company runs more than one hundred projects on a single instance server. Besides core IT projects, we have implemented business processes on dedicated JIRA instances to manage high volume (greater than five thousand issues per month) non-conformities for some business lines. 

Transparency of development projects, as well as approval processes for some business projects, has improved massively. Interaction of business units and IT happens very often via JIRA and considered to be very helpful. As many of our developments are requiring some level of compliance, the workflow and documentation of approvals are very handy. 

There is a very flexible configuration of "issues" and related life cycle. On top of it, the number of "add-ons" is overwhelming and of very good quality. I would consider the reporting capabilities to be the best feature, as ultimately the visibility of issues allows management of the projects.

My main concern is the administration of projects, especially user groups, and this requires root access rights but there is no concept of layered admin rights. Projects can be managed by a limited admin, but the creation of projects needs root admin rights. In decentralized project ownership, this gets tedious.

We used an open-source system called Mantis, which was considered unsuitable for use outside the IT world.

The setup of JIRA is straightforward.

To try this solution, use their cloud offering to get familiar. After that, it's in my view worth the money.

We went right away to JIRA without evaluating other options.

JIRA, its add-ons, and the Atlassian product world are already very powerful and it is difficult to name significant blank spaces.

This is a very powerful solution. Get some advice and training to make the most out of it. You may miss out on some of the capabilities if you don't.

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 am the software developer manager and I use Jira to manage team performance. We're also starting to use Jira for our drives. I used Jira before, for creating user stories from boards, to discuss issues, and many other tasks. Today we use Jira, Confluence, and BitBucket in our work. We practice scrum in our organization.

It improved with many exiting features to manage user stories, planning and retrospective meetings very productive.

The documentation is very good.

The solution is stable.

You can scale the solution easily.

It's comparable to Azure DevOps.

It's a very complete product overall.

It would be ideal if Jira had future functionalities to integrate more easily with various aspects of code reviews.

It would be nice if, in the future, Jira worked a bit more like Azure DevOps in order to be able to manage work in progress and have the task measurements in strategies for the stories.

In the future, I would like to have traceability features. For example, when you create a task or a sub-task that's related to code. In this task, if we could create a method for retrieve customer information, that would be helpful. In that case, I would want to train with the source code later.

I'm new to the company. Although I've worked with Jira before, I've only been at this company for one week.

Atlassian solutions for me are very good solutions. They are very interesting and very productive. As a user, it is necessary to have a unique portal to make traceability between sub-tasks related to code or programming. You can create and screen or implement a function or a class, related for example to the code that you are pushing in the repository or commit in the repository. If I open the sub-task, I will see the code related to the sub-task. It's very similar like Azure DevOps. Azure DevOps, however, has this functionality for traceability. This functionality will be amazing that Jira would implement something similar.

I prefer to use Azure DevOps instead of Jira for stability or the frequency of use. In my case, for example, I feel that more users, more companies don't think Azure DevOps makes a good choice due to the fact that the cost is higher than Jira.

The scalability is very good if you're carrying a lot of projects here, and if the company needs to have a lot of people to PEA development centers in Mexico. Our technicians can easily test the tool and scale it in order to develop projects.

We do plan to increase usage. We're already training more users. We're increasing quickly so that our teams will be ready for upcoming projects.

We have manuals, technical support, and also technical specialists in the company. I haven't had the opportunity to use directly call the technical support from Atlassian, however, the technical documentation that I have reviewed is excellent. We're satisfied with the level of service we have access to.

We also use Azure DevOps. They are both very similar. The main difference is Azure offers traceability.

The solution is easy to implement. We have the cloud version of Jira in the company, and we don't worry about maintenance, it's automatic.

The cost of Jira is okay. It's better than Azure DevOps. We don't have any licensing fees that I know of.

While I'm new to the company, it's my understanding that it is a partner of Atlassian.

We use the latest version of the solution, as we use the cloud, which updates automatically.

Our company has both Azure DevOps and Jira. I use Jira, and Azure DevOps is used for other purposes. Most projects, all projects that are using Azure DevOps are legacy projects. The new projects and new solutions are using Jira.

On a scale from one to ten, I'd rate Jira at a ten. It's a very good product.

Both tools, Azure DevOps and Jira are at the same level. In terms of preference, I typically choose Azure DevOps for familiarity but not for features. For features, both are the same. For example, Jira has amazing features that Azure DevOps doesn't have, and also Azure DevOps has the flexibility that I like very much. Both tools have different interesting aspects. However, if Atlassian would implement traceability, I would prefer to use Atlassian. For me, it's more complete and allows for smaller teams than Azure DevOps.

Jira is a project management tracking tool, and it would be great to see integration with the source front or Azure DevOps, etc. The history of tasks, such as check-in and checkout, is not maintained under the particular Jira ticket. For example, in Azure DevOps management for a work item you can find out any chain set and dependency.

I've been using Jira for more than two years.

It is a stable solution.

We have around 2000 plus users, so scale wise, there are no issues. We can easily scale up with multiple users.

I'm coming from an Azure DevOps background, and we use the integration board. It is very easy because the source code is there under one umbrella; however, Jira is not under the Azure DevOps umbrella. If your company is using Azure DevOps or Git as a repository, I recommend using the Azure DevOps board rather than Jira.

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