Jira Reviews

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.

We use Jira to manage what is happening in our projects, such as application development lifecycles.

The most valuable features of Jira are the dashboards and user interface. The processes within Jira to monitor, maintain and release are beneficial. It is a continuous development solution.

I have used Jira within the past 12 months.

Jira is a reliable solution.

I have found Jira to be scalable.

The price of Jira could be lower.

I rate Jira an eight out of ten.

We use Jira for ETCM. It's for ticketing with QRadar.

We integrate Jira with QRadar which is helpful.

The performance is quite good.

It has real-time collaboration. 

It provides good visual data easily.

While Jira integrates well with QRadar, it is not integrated with Splunk for example.

I would like to see more integration available with more tools.

Jira is not used in my company; in fact, it is not used at all. Jira is a project management tool that I use at school and during my internship.

Jira is stable. I have not experienced any issues with the stability of Jira.

We have not had any issues with the scalability of Jira.

They provide technical assistance. Whenever you need something technical, they are quick to respond.

The price seems reasonable to me. It's very similar to Splunk. 

I don't believe it is expensive. 

I'm not sure if they provide a free version, but we need free versions of everything to try before we buy. 

I believe we simply require a longer, free version.

The initial setup is simple. I didn't do it myself, but I've read the support, the guide, and it appears to be simple.

I did some research for a school project. I needed to compare it to Splunk and a few other tools. As a result, I'm not particularly interested in purchasing them.

I don't use Jira very often, and I don't have a lot of experience with it.

I would rate Jira a seven out of ten.

Our primary use case is for project management and defect tracking. We are customers of Jira and I'm the quality manager. 

We use multiple plugins and tools which are integrated with Jira. It provides good output as we expected and we are basically hoping to increase the number of users. It's a user-friendly solution. 

I think the automation feature needs to be more user-friendly because not everybody knows about coding. The automation should be customized so that it's easier to use. 

I've been using this solution for four years. 

Stability is great now that we've moved to the cloud. 

Scalability is good. We initially had 100 users and we now have 250 without any problem. 

The support is good and available whenever we need it. We have been interacting with them for our query resolutions, as we have certain challenges that we're dealing with day-to-day.

The initial setup was quite straightforward. We used an integrator for deployment. We have a dedicated team for maintaining Jira.

I would recommend this solution and rate it nine out of 10. 

We use it for Kanban boards, bug reports, and some workflows.

It has enabled us to keep track of features or projects. Previously, we used to manually keep track in Office. We now have a centralized repository for all the information.

I like that you can comment almost anywhere, and you can leave a trail. That's the most useful thing.

I don't know if it's the way it's deployed in the organization, but the interface we are provided is not as customizable as other tools. The multi-language report is not enabled in our installation. I don't really know if it's something related to the tool or our installation.

It is pretty good. I haven't had any problem with it.

We haven't had any problems with scalability. It doesn't feel slow. It hasn't been down. It's working pretty well.

Its users are in the hundreds, but I don't know specifically. It is available to everyone in the company, and it could potentially be used by anyone. We all are allowed to use it and implement it as we see fit.

I have local technical support. That's our first line of support, and they contact Jira technical support if needed. 

I'm just a user. I don't know.

General advice would be to find out about customization features and multi-language support features.

I'm not a heavy user of this solution. From what I've used, I would rate it an eight out of 10.

Jira is used for issue tracking and defining the development pipeline. It's helpful to define when a project is done and track a task as it moves through different stages. The deployment type varies based on the customer's environment. We sometimes connect to the client's setup, which can be in the cloud or on-premise. 

I like that Jira allows you to customize the flow for an agile process and adapt it to your own flow.

We've used Jira for around 10 years.

We evaluated Jira for security and stability, and everything went well. 

Jira performs well and scales up enough to meet our needs. We probably have about 200 users, so we don't need more than what it offers. 

We used a solution called Mantis a long time ago. We're a software outsourcing company, so we adapt to our clients' setup. Plus, Jira serves our needs well, so it made sense for us to work with that. We don't recommend anything else. We use Azure DevOps, Jira, and Confluence on our projects. If it's not in Microsoft, then it's Jira and Confluence.

Deployment isn't something I handle personally. Our DevOps department does that, or it's installed by the client, so I'm not dealing with it either way. One engineer is enough to deploy.

I don't know the price of all the setups. Our clients pay for the setup, so our Jira users are covered by them. Of course, the price could always be cheaper.

I rate Jira nine out of 10.

We use Jira for software development and issue tracking, enhancement requests, and software lifecycle management.

Jira has benefited the organization because it's necessary for doing our job well. We would need to have Jira or a similar tool. For example, it's could be similar to working with documents, you need Word or a similar tool.

The most valuable features of Jira are all the integrations with other systems. It's not the best in any specific area but it has lots of plug-ins and integrations.

Jira could improve the workflow, screen, and field configurability. They are lagging behind other solutions, such as Allegra in work system configurability.

It depends on your usage pattern because if it's more configurable, you can configure it to be a very different kind of tool which is a benefit.

I have been using Jira for approximately 10 years.

The performance is not very good for Jira but the reliability is good.

Jira can handle a lot of tasks. In my project, we have approximately 50,000 issues to be resolved and it worked well. However, the overall solution is slow.

We have approximately 25 employees using Jira in my organization of a total of 2,000 employees.

I use Jira moderately while other of my colleagues use it daily.

I have not used the support from Jira.

I have been using Allegra previously.

I was not around for the initial setup. However, I tried to configure it later and it is not easy. It is not as easy as it should be.

The solution is on the cloud, there is minimal maintenance.

The price of Jira is reasonable.

My advice to others thinking about implementing Jira is if you only want it for the standard flows and use it as an issue tracker in a software development setting, it is a good solution. We are using the online version. If you are in need of changing workflows or appearance, fields, screens, et cetera, Jira is not able to do this well or it's not possible at all.

Jira has found its place in our organization and it does those tasks. They should focus on speed and stability, and in that order. It's excellent with regards to preexisting integrations but it is poor at configurability.

Whether Jira is a good solution for you depends on your use case. From what I have seen creating different workflows in Jira is not good.

I rate Jira a five out of five.