Jira Reviews

We have various use cases for it, one being for object storage. It's a government entity so that's what they use. 

It has improved my organization because it gives us collaboration. 

The most valuable feature is that it is somewhat flexible. 

It's a pain getting it on the public, it costs too much.

It's also difficult to migrate through, things don't always tie-up. It's not easy to use and it's not as intuitive as it should be. I stay away from it as much as possible.

I have been using Jira on and off for ten years. 

I would say that it's stable.

I would rate it a five out of ten because it gets the job done. 

Jira is the best project and defect management tool. It works very well for all types of software methodologies or cycles. Communication is very clear to the whole team members. My team relies on this software to keep track of what we are doing. It has lots of nice features that we use such as to link issues to one another, link tickets, put labels of versions to be released, and story points. As a QA person, I also use the filters a lot to find issues that are assigned to me or have been reported by me.

JIRA has helped us to organize our projects and keep them organized. It has also allowed a great deal of transparency into the development process for management which has greatly reduced the workload on project managers by automating some of the report generation necessary to show progress.

This software helps us to follow the process the team agreed to and see the progress on issue and sprint level. With the help of this tool, we will be able to track the progress of the issue and sprint.

The reports and dashboards do not provide for reports in a graphical way. The tickets cannot be simultaneously assigned to two or more users.

Jira makes life easy — best tool to use in agile projects!

This product enabled us to grow and not lose productivity in the process. We were able to maintain a good line of sight to what teams were producing and which ones were on track and which teams were off track.

I have not used any different solution.

I have used this tool as an in-house one.

Customization of workflow is a key valuable feature. JIRA comes with a few default workflows, however you can create highly customized workflows depending on your needs.

Tracking more items in JIRA allows for more transparency of projects; centralized access to latest issues, risks, tasks, etc.

Improvements for Cloud version. One such item is available of nested user groups, which is available on server version. Managing a large number of users on Cloud version is extremely challenging due to lack of this capability. I wrote my own command line admin tool in order to manage users more easily.

I have used it for two years and was the main admin also.

We used the Cloud version, due to external access needs. Cloud version deployment is just configuration.

With more users and more projects, administration becomes more difficult. Administration is very manual. Thus, I had to write my own command line tool to automate some of my administration.

Customer service is good. Response to support requests were fairly quick.

Technical support is good.

Initial setup is straightforward. A large user base and/or large number of projects requires more planning and strategy, so that you can re-use common workflows, rather than create new configurations for every project (think of abstraction is object-oriented programming).

Pricing is based on the number of users. Cloud is cheaper, but choose in-house (server) version if you can, as it has more features and is more secure; overall very affordable.

We looked at RedMine (open source), but features were limited, and it is not very user friendly. Other options such as BaseCamp and Asana were not really comparable products, in my mind, even though they come up on many comparison websites.

JIRA is tool. As with any tool, it needs to be in the hands of the right person to be used effectively. The administrator and/or trainer in your company should be very competent with JIRA, as they will be leading the effort. JIRA is powerful, but what truly makes it a powerful tool is integration with other Atlassian packages and third-party software. JIRA should almost always be used in conjunction with Confluence. There are many integrations available such as GitHub and many other applications.

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 use Jira in our organization for lifecycle management.

The solution has helped our organization do lifecycle management easily.

I have found the most valuable features of Jira to be ticketing, life cycle workflow, definition, and creation. Many of the features are useful.

The solution could improve by having its own tool for quality lifecycle management.

I have used Jira for approximately nine years.

The stability of Jira is good.

Jira has good scalability.

We are using this solution extensively. We have more than 5,000 using the solution in my organization.

We have been satisfied with the technical support from Jira.

We have used in-house developed tools previously and we had to do a lot of customization and this is why we moved to Jira.

I would recommend this solution to others, it is a good option.

I rate Jira an eight 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.