Jira Reviews

1. "Start watching this issue" which sends updates to a user who has subscribed to this JIRA when there are changes made
2. It provides us with a view of historic changes that are recorded
3. It allows universal searches, even across multiple projects in JIRA, when we want to find the JIRA where a keyword was referenced

We use this as a primary tool to record all requirements and changes. This product is absolutely easy to use and does its job perfectly. 

My opinion of this product is that it is quite complete - from a QA standpoint.

I've used it for four years. We have this integrated with SpiraTest, so all incidents raised in SpiraTest are replicated over to JIRA and vice-versa.

JIRA was the solution we used throughout. It had no competition.

This is a good product, and I would back it every time.

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.

Customer Service:

It's very good.

Technical Support:

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 this solution for our scrum team and user story management.

This solution assists us with being able to quickly and easily start sprints and keep accurate track of them, including billing using a time-tracking add-on.

This solution is very easy to set-up and use. It is very intuitive.

The permissions can be challenging to get right.

We have been using this solution for five years.

Requirements management.

It enabled us to track and manage product commitments over the entire enterprise.

One form for each feature/item.

Better ability to add numbers in ad hoc queries and search results, e.g., total development cost estimates.

We didn't use a different solution.

It's really for Agile projects with storyboards, and then defect management.

The performance has been okay.

It has improved the Agile process in our company.

A lot of people in the business work with this tool so when you are searching for a new employee you don't need to train them on this tool. 

The reporting and the view, from a story to a defect, should be improved in the next releases. For example, how many boxes are assigned to one story, or how many tests are run on one story, and so on. This is what I miss in the tool at the moment.

The stability is very good.

We are about 700 - 800, and it works. Not all use JIRA but in IT we are 100 people.

I have not personally been in touch with support, but I think the support is very good. I haven't heard anything wrong with it.

We have two organizations. One is development, and they work JIRA. And the other is the business, which is responsible for testing. At the moment, we are going in the direction of DevOps and more Agile, and we would like to merge our tools together.

The important criteria when selecting a vendor, in my opinion, are that the vendor should be flexible, cheap, and the support should be excellent.

I rate it an eight out of 10. It's easy to use. People can become productive with this tool in a short time, and it is really the right solution for an Agile environment.

A lot of solutions show very well on paper. When you are selecting a solution, do a proof of concept in the environment.

One of the valuable features is traceability from requirements to test cases.

Traceability was not available before. This is a great advantage for audits

I would like to see test execution modules.

We have used this solution for three years.

We encountered only a few issues with stability.

We did not encounter any issues with scalability.

Technical support is good. We use Beecom as the provider.

QC was used here, but I do not know why they made the switch.

JIRA can be parametrized quite intensively. Once you understood how it works, it works well.

We started here with this product, after the decision was made.

Use Beecom as the provider.

User friendly, easy to set up and maintain. Great integration along other Atlassian tools. Application can be enhanced either with free plug-ins or you can create your own.

Seamlessly merged efforts between quality and R&D.

Missing a Requirement Management piece on the suite.

Maintained by a big company. Simple installation process. Extremely customizable. Front-to end exposure (repository, issue tracking, feature management, etc.). Enormous user base with lots of exposure. Add-on plugins. Excellent documentation and support. We can take advantage of the 10 user certificates of confluence and green hopper. Will be good to use when the project is going to start.

Generally, customization, granted that it is done only at system productions state, is hard and time consuming. Most of functionality that is not required for use of system, cannot be deactivated; you need to dig through all superfluous stuff, in many cases. Even though JIRA documentation is immense and solid, filled with tutorials, you really need docs, to use JIRA, the system is so complex that you need to read docs almost for every customization task and even then, some views are hard to understand.