Jira Reviews

The features mentioned below were quite useful for me -

• Project tracking

• Planning

• Defect management

• Code integration

• Service Desk

• Email notifications

• Reporting

In my organization, we have so many diverse projects, that the flexibility to integrating JIRA with other tools has been a helpful feature. It has streamlined and channelled our project and test management activities. This has helped all my organization's departments as we now have a data-bank that means anyone can access the required information with a few mouse clicks; be it someone from sales, QA, developer, or management.

The only problem area for me is applying filters, and for new users it is very complicated work. I hope they can come up with a better filtering functionality, as this is one of the most basic, important and most widely used features by all categories of users.

I have been using different versions of JIRA for the last three to four years.

No issues encountered.

No issues encountered.

No issues encountered.

It's very good.

It's very good.

We previously used Quality Center, but JIRA offers better value for money.

The initial setup was straightforward if you know the basics of installation.

Through a vendor team and they were real experts in JIRA.

I can not give you details but the ROI is excellent.

JIRA's pricing and licensing is the best in the market with the features a user gets.

• Quality Center
• Mantis

This tool has some good bug tracking, issue tracking and project management features. One of the best feature is its integration with other tools which I love, but at the same time, it has some limitations as well.

This is a great product, but I always say before jumping into using it, go through the user guide. Also, if possible, look for some tutorial videos to get the full use of its functionalities.

We are using it for project management. We have cloud and on-premises deployments of this solution, and we are currently using its latest version.

It is very straightforward and easy to use.

It should be less expensive.

I have been using this solution for about five years.

It is scalable. We have about 500 users.

I don't have any experience with their technical support.

It is easy to install. It takes one to two days.

Our team handles its deployment and maintenance. We have a team of three people to manage it.

Its price is fine, but we would like it to be less expensive. We are paying on a yearly basis.

We didn't evaluate other products.

I would 100% recommend this solution to others. We plan to keep using it.

I would rate Jira a nine out of ten.

The integrations with other solutions, such as BitBucket for pull requests and the check traceability, are pretty good. That's about it. I'm not a big fan of the solution overall.

The initial setup was pretty straightforward.

The solution, in general, is a poorly designed and confusing product. The user experience is not ideal and the user interface is convoluted. The interface in particular could use a big refresh as the actual navigation within the interface is not particularly smooth.

The work items structure is not hierarchical and that needs to be changed. It's too flat.

There's excessive scope for customizing the project and the platform. Therefore, there are too many integrations, which leads to very high levels of complexity in terms of management.

Key indicators that are useful to Agile teams such as burn-down charts or burn-up charts, cumulative flow control, et cetera, are available, however, they're not easily accessible from the default user view, whereas they should always be present. Key indicators must always be present. They actually take a couple of clicks to actually get to them.

I've been using the solution for two years. It hasn't been too long.

The solution is very stable. It doesn't crash or freeze. There are no bugs or glitches. It's reliable in that sense.

The solution is scalable. If a company wants to expand it, it can do so.

We have about 200 people who use the solution currently. They're mostly software developers but they're end-users as well.

While the solution is being used extensively, we're fine with maintaining our current level of usage.

Technical support is very good. We're satisfied with the level of support that is provided to us. They are knowledgeable and responsive.

I've personally used lots of other solutions, however, when I moved to this company, they already had Jira deployed. Jira is the only system of its type that's been used here.

The initial setup is not very complex. It was pretty straightforward. If a company wants to implement it, the setup should be pretty simple.

There's ongoing integration work on a project like this. Therefore, the initial setup was only a few days, however, then, as you add things to it, you add more time to the deployment.

We are a customer and end-user of the product.

I would highly recommend not using this product if your focus is software development. Organizations should seriously consider alternatives such as Azure DevOps or TFS, which are more focused on modern interfaces and more accurately modeled to modern workflows.

I'd rate the solution at about a three out of ten. It doesn't really offer a whole lot that's actually usable from a software development context beyond extremely simple and free alternatives.

We are using Jira as our help desk solution, as well as for managing our software development efforts.

Jira has helped with respect to managing our software development, although it does not suit us well as a help desk.

The most valuable feature is managing software development.

The help desk and services management features are in need of improvement.

I have been using Jira for five years.

This is a stable product.

The scalability is fine. We have fifty people in the company who are using it.

I have not used the vendor's technical support.

The initial setup was done before I joined the company.

I am currently in the process of searching for better help desk management solutions.

My advice for anybody who is considering this solution is to ensure that it meets your requirements. For example, we have been trying to use it for help desk management, but have found that is not well suited for this task.

I would rate this solution an eight out of ten.

Full SDLC, from software development to quality assurance tracking and project management. The applications of JIRA workflow management are endless. 

Tracking and accountability have been improved, as with the advanced workflows, one can ensure processes are followed, and it is easily seen through one of the many reporting options exactly who is doing what and when.  

Workflow management as very specific workflows can be configured to serve any number of business processes. 

The downside to JIRA is the constant push for the changing of the user interface. This can remove valuable features and increase the learning curve. Especially for business users, the change in interface design instantly reduces productivity and buy into the tool.  

Overall, everything with it is great. I found it super useful, as it is customizable for different teams and users.

The following definitely need improvement:

• UI 
• Speed 
• Mobile app functionality.
  

It is consistently slow.

I use Jira for user stories, tasks, bugs, track releases, track backlogs issues, burndown, and test reports.

Jira has helped our company because it is easy to track releases and deployments. It is easy to track which tickets have been done or are still pending and left to be completed.

Jira's most valuable features are ease of use, simple to understand, and highly flexible. Additionally, you can use kanban or scrum which is a benefit.

The reports in Jira can be improved, especially for test reports. I find it difficult to customize and integrate for different testing purposes.

The out-of-the-box version of Jira has minimal to no testing functionality. I have to use Zephyr to be able to track testing. The time logging is also not easy to use, or user-friendly.

In the next release of Jira, there should be test cases in the test reports. Better burndown and burnup reports should be enhanced. Additionally, the usability of time logging could be better.

I have been using Jira for seven years.

Jira is stable and reliable, we have not had an issue.

I have found Jira scalable.

We have approximately 50 people using the solution in my organization.

I use the solution extensively in my organization, I use it daily.

I have not contacted support from Jira.

When I came to this company I had already used Jira. Previously, I was using quality control from Quality Center and Azure DevOps.

The initial setup was straightforward overall. The process takes only 10 to 15 minutes. However, the setup could improve.

We did the implementation of the solution in-house.

We have two administrators that do the patching and maintenance of the solution.

I would recommend Jira to others.

I would advise others to be sure to do the reports correctly because there can be some challenges in reporting and in the testing phase.

I rate Jira an eight out of ten.

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.