Jira Reviews

JIRA comes with a workflow designer which allows to design and keep track of execution of pretty much any process (similar to what a BPM solution would do but cheaper). In the new or existing workflows you can define new "statuses" which you can use as "Queues" to handle your process status or requests.

In principle, JIRA was designed to follow software development projects, but we are also using it as a solution for our call centers to follow on "Learning Administration System" processes.

It allows you to extend and define any new entities (record types), define sub-tasks, links between records as well as define new fields, screens and customize your UI based on your needs.

It also integrates very well with other applications thanks to its Restful API. In my case I integrated with JIRA from Webmethods EAI middleware as well as from SQL Server 2014 SSIS.

JIRA has a marketplace where many plug-ins are available (some for free) to extend any missing features, as well as it comes with an SDK to create your own one if needed. In fact, this is one of the biggest potentials from my point of view.

Among others Atlassian (JIRA's company) has two powerful plug-ins

• Service Desk (to control SLAs in top of your processes) - actually not a plug-in a product on top of JIRA.
• JIRA Agile which allows to follow Soft Dev Projects using SCRUM or KANBAN methodology.

• We deployed JIRA and JIRA Agile plug-in to keep track of our software development cycles using SCRUM methodology.
• It has been our product of choice for some time now in order to deploy Learning Administration Systems for our customers.

I strongly believe that ease of use for the administration part (workflows, screens, field definitions) could be improved. Sometimes it is difficult to understand "where you are" when administering JIRA.

As a Test Analyst my first requirement is to have a tool where I can create a repository for all my test activities like test cases, test execution, defects and reports. Zephyr is an add-on which provides facility to use JIRA as a test management tool. We can write test cases, add versions, create test cycles and execute cases. To make life easy JIRA comes with a dashboard where I can add different gadgets to generate reports on different criteria.

My organization uses Wiki and JIRA both for requirement gathering, but very few know the capability of JIRA as a test management solution. People in the past used to write and execute test cases in WIKI and also log the defects from there. This not only made it difficult to manage the test cases and defect, but also there are no reports which can be extracted out of it. It becomes very difficult to fetch efficiency in each test cycles. Also, we were not able to track test coverage because we couldn't link requirement with test cases in Wiki. But after JIRA provided us a feature to use it as test management we are managing all these very effectively.

Though JIRA can be used as a Test Management tool, it is not complete by itself. There are still a few niggles in it as compared to other products like HP ALM. We can export the reports in xls or pdf. Also whenever we fail any test steps, the test does not fail by itself, we need to manually select fail from status drop down. JIRA does not provide any lock feature for a test case if any person is working on that case. In fact, both people can assess the same case at the same time.

I've been using JIRA for the past 2 years.

I found JIRA to be a stable product and didn't have any issues with the response time as compared with HP ALM. Only a couple of times during last 2 years it was down for few hours.

I worked on HP QC 9 & 10 before JIRA. There were no issues with these tools to switch to JIRA, but the tool used fora project always depends on management, user benefits and cost involved in it.

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.

1. Its agile support is fantastic! Whether you are an agile expert, or just starting for both scrum and kanban teams, the whole agile process is supported
2. Requirements log
3. Story board
4. Dashboards are a great feature to stay on top of what is going on in all the projects you are managing
5. It's accessible from practically anywhere, whether you're on a mobile device or desktop across many OSs and browsers

Integrating JIRA with HP Quality Center gave our dev team and management a new window to participate/track the defects Testing Team reports from. This integration is absolutely powerful and made defect sharing with different parties a peace of cake. Now we, the testing team, can report defects on our own "beloved" HP QC, and these defects gets sent automatically or upon request to different JIRA Projects and to different project parties and teams.

I would say test management, as it's a generic issue tracking tool, and not designed specifically for test management. So, the only support for test cases is the ability to mark them as passed or failed as part of the test execution, and that's the whole test, not step by step like Quality Center. It does have many test management add-ons that can be bought, and some of them can perform close functionality to what HP Sprinter does, like Bonfire, but it does not provide video recording. It doesn't provide version control for Test Cases, and integration with Test Automation and Performance Testing tools is cumbersome.

I hate the fact that I have to buy an add-on for each feature I need. Some people might see this as positive thing since you buy only what you need, but again, not all add-ons are provided by Atlassian, and hence support and quality is subject to different providers, which is again is cumbersome, and not many people would go on with.

Reporting also needs improvement, as I need to be able to create my own custom reports and be able to export them, and screen shots doesn't work all the time.

If you are an agile development team, go for it. I would advise that f your dev team have problems accessing HP Quality Center, go for it and integrate Jira with Quality Center.

JIRA features are agile planning and release notes. We heavily use the Service Desk to support our product customers, and we also provide support for our services customers via JIRA tickets with a time tracking plug-in so invoicing, project status, are available to everyone us and our clients, keeping us on the same page.

We are now using this system for all time tracking of internal non-billable projects, support contracts, development tasks and billable work. We can see our resources utilization and track how much time was spent on each client, which is good for invoicing, on Go2Group made products. This helps with our ROI on a product by product basis, and we even track our time off in this system.

It has enabled us to be on the same page with our client’s they can see the tasks and burn downs and exactly where their money is being spent. When we combine this with the Confluence Wiki, we now have a very robust Q&A and documentation page. We use it for sign-offs and online documentation. There is a history of what folks have done, and the information is radiated out in near real time. It is all there.

We can serve multiple clients, our own internal products, projects, and operations from one system cutting the resources needed to run these systems. Compliance is much easier to achieve, documentation, you need to sort out what needs to be displayed and reported in the formats you wish.

All in all, these tools, with little effort or cost, have allowed us to provide, what larger consulting and product firms struggle to provide due to legacy products/system/acquisitions, and compliance.

A more enhanced Service Desk module, with support for more types of alarms and the like.

The product is very easy to download, and install. Once downloaded, you just click next, OK, then viola! You are a newly minted JIRA Administrator, it is too easy. Teams, company data, and processes end up growing from grass roots movement before management realize it.

While Atlassian and TFS seem to be more of the toolsets that companies are adopting, and they are great core ALM stacks to build upon, you are still going to need tools from other vendors for most environments. For instance, you have more strenuous support desk needs, there is ServiceNow. If you make cars, boats, aeroplanes, trains, etc., you will most likely need IBM Rational DOORS. High end testing is still the domain of HP ALM/QC. Aerospace higher-end agile planning, you could look at JIRA Agile or VersionOne, or Rally. Embedded C, etc.

To summarize, MS TFS and/or Atlassian (maker of JIRA) are good core ALM stacks to run your shop on. The remaining issues are generally around how to integrate other systems to TFS or Atlassian, and also, how to migrate to TFS/Atlassian.

We are a heavy user of the Atlassian tools and are a reseller. We do VAR work for other competing ALM solutions as well, notably Microsoft, IBM, HP, Perforce, etc. This is just the toolset we have grown into.

Then they look into the systems and realize what risks there are and are usually slow on the uptake to designate these systems as Class A or B critical systems. They may be surprised at how many individual systems have sprouted across their organizations. You can find yourself in an organization with multiple JIRA instances due to the grass roots nature of adoption, with dozens of workflows and hundreds of custom fields in each instance.

It can be a lot of work to pull these together under compliance and DevOps. Would be much easier to accept these tools as mission critical, or at least realize their importance, and grow them correctly.

Defect Management, Issue Management, and the GreenHopper plugin with Agile.

They should provide CLI or some other deployment mechanism that improves productivity by avoiding duplicate efforts.

6 years as a user, and 1 month evaluation period

During an upgrade we found an issue.

Yes, this is not stable as compared to other tools I managed.

Yes, scalability is an issue. Performance decreases.

7/10

7/10

Straightforward

Ourselves

I would rate it a 5 on scale of 10, but again it depends how large is the team, company size, overall features needed and the instance you want to manage.

When we used it, it was a low-cost solution but now the costs have increased. The team has to look into long term costs.

Yes, other defect management tools available on the market when I first evaluated JIRA 6 years ago.

UI of this tool is good.

Small teams and small projects may consider this as good option.

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.

Usability for our users and flexibility for our admins.

JIRA and Confluence have taken off here like wildfire. Our users enterprise-wide have made excellent use of these tools.

Performance and Scalability in a large enterprise could be improved.

4-5 years.

Not with deployment, but growing pains as fast as we have grown in the last few years with JIRA. We now have 7 different instances of JIRA.

Yes – we wished we would have stayed on the simple path of using the product with fewer add-ons and customization. Most of the complexity is add-ons and customizations that we have chosen to do and likely we have taken some of those too far.

Yes...We would really like to see JIRA scale into 10-100 millions issue range.

Took some getting used to but great!

Took some getting used to but great!

We switched because we wanted to remove over 3000 Lotus Notes applications. 30-40% of those applications were replaced with JIRA or Confluence.

Atlassian products seem to be very simple and straightforward if you use it simply and stick with what comes with the product. The complexity and complication comes when you introduce add-ons and customizations. The other observation is that Atlassian products seem to be less ‘conditioned’ for larger enterprises.

The ROI on Atlassian products has been tremendous. It’s been well worth the investment!

We chose JIRA/Confluence as they were solutions we can get up and running quickest, and also cheap.

Keep it simple. . . minimize the add-ons and customizations!