Jira Reviews

We use this solution because it comes with some of the products that we are using. It is a part of the package. Our usage is quite basic, and we have not finished exploring and deploying the whole solution.

It is a complete solution. It has more features as compared to other tools, especially the open-source one that we use. It is also easy to administer.

Based on the feedback from my admin, it is sometimes difficult to find some of the features. It is not a big deal, but its configuration interface can be improved to make it easy to find things.

I have been using this solution for three years.

It is very stable.

We have not deployed it on a very large scale. For now, we have ten users, and it is mostly used for our internal things, but from next week, we're opening it for the community. We'll have a broader experience of the product.

We haven't used their technical support so far.

I have not heard of any complaints about the installation. It takes almost half a day to install. It took some time to configure it for different tools that we use, but the installation was straightforward. There is enough documentation for its installation.

We did it on our own. I only have one admin guy for its deployment. 

We are a regional research and education institute. We're using the free license provided for educational institutes.

I would recommend this solution. I would rate Jira an eight out of ten. 

I use this solution for general issue management, software planning, and change management.

This solution is a one-stop-shop for issues and plans.

Issue linking has enabled teams to trace issues.

I like the dashboards and Kanban boards.

The development links to GitHub are critical.

The only thing that JIRA doesn't for us is release management in a way that I can create a list of versions easily.

Perfect for keeping track of large amounts of bugs, tasks queries and releases for fixes. 

The SaaS does the job it is supposed to: helps you keep track of your projects. What I like most is the ease of adding users and the obvious nature of what they need to do -  drag and drop is always a win. 

It is cross methodology so Scrum, Kanban... it doesn't matter, you can use JIRA.

I like how it shows the sprints remaining. Being able to instantly see where you are in a project and what is coming up is invaluable. 

Also, the ability to link a programme of projects is very helpful. I can see where all of the teams are with their individual projects but also how they fit into the overarching business plan for the year.

In reality, it's allowed me to raise and keep track of 700 tickets (bugs, queries, tasks etc) effectively. I can track what tickets are in UAT and which ones are coming out in the next software release. It's very simple. 

It allows all of those involved in a project, to see what stage their deliverables are (depending on what you allow people to view, they can see all deliverables from all teams)

Keeping everything in one central place with it obvious as to who is responsible for what, is a fantastic thing. 

It gives programme managers an overview of how a slew of projects are going. This also provides information for Exec meetings/Board meetings - visuals are always helpful to instantly show people what is happening with a programme of improvements.

Basically it allows me to see what is happening very quickly. 

I have no areas of improvement that I would push. JIRA does what I need - it allows me to assign tasks and to update my project. Any problems that I have found have been more to do with people entering with a lack of details - rubbish in = rubbish out. But that is the same with all apps.

I've used JIRA for over a couple of years, in three organisations, so I have some experience of how different places use it.

SaaS so nothing to deploy really. 

There's been the odd amount of JIRA downtime (not self hosted) and sometimes tickets that can't be accessed. 

I've not had need to contact the customer support team so I suppose that is a good thing.

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!

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.

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.

We primarily use the solution for all issue reporting. The business uses it and we use it in IT as well. Any issue, anything from the help desk to software issues use Jira. It can house test plans, test sets, test executions, and provide some reporting. It's the reporting that's important for us.

The product has formalized the workflow process for reporting tracking and stacking and processing issues. It's also added some formal approvals, just for the purpose of formalization of a process workflow.

If you're using it in an agile shop, the traceability between epic story's test case defects is very helpful. 

I like that all of the team members on an agile team can use it. No one is in a separate application.

The stability is good.

The product can scale, so long as you have storage.

The reporting needs to be better. Being able to do some test management would be useful. In the tool, it would be ideal if they could give you some out-of-the-box reports for things like requirement coverage and regression and things of that nature.

I've used the solution off and on for about four years. I used it when it first came out to do some evaluation and we implemented it at a startup. That was when it first started. I've probably only really used it for about eight months on a daily basis.

We have had no downtime, and therefore I don't have anything to say that would be negative. It seems to be quite stable. There are no bugs or glitches and it doesn't crash or freeze.

As long as a company has the money for storage, it's scalable to any size. A small company can use it or an enterprise-level company can use it. It works for both.

Currently, we have less than 1,000 users in our organization using the solution.

Jira is extensively used in our organization.

We do plan to increase usage as well. The company purchased it so that it would be scalable. There's not a solid plan right now to add measurable users or increase the size, however, we know that it's available and that's what we were looking for - something that is scalable. The plans are to grow and as that growth happens, either organically, or via the purchase of other financial entities, we can grow the size of the database application and the number of the users.

I did not personally use technical support. I have worked several months with the people who have, and they say that the support is very good.

If the company used something previous to Jira, it was before my time. It possibly could have been Sharepoint, however, I was not with the company at that time.

The solution was implemented before I came to the company.

That said, my understanding is that the company tried to use as much out-of-the-box functionality as possible and it was quite an effort. They spent quite a lot of time formalizing workflows and things of that nature. In the end, it was very well thought out.

We do have a team for maintenance and what takes the most time with any upgrade is going through the changes, the enhancements, the defect fixes, and things like that. The actual time that it takes to physically update it is pretty minimal. However, going through the documentation and meeting with the team to make sure that we have testing covered prior to upgrading is work. We have a test environment prior to pushing it to production. That's what really takes time. It's not the physical update. An update might take two and a half hours and there's a lot of data in there.

My understanding is the company used professional services from Jira and also got some training and stuff of that nature.

We're just customers and end-users.

We just upgraded the solution. We are on the latest version.

I'd advise potential users to make sure that they talk to the people who are going to be testing and make sure that they know, what metrics they need before they pick a tool, any tool - even if it isn't Jira.

I'd rate the solution at an eight out of ten.

I believe we are using the latest on-premises version. 

Confluence, not Jira, is the most convenient feature with Atlassian. We use the product for knowledge management, the use of creating or documenting knowledge into a knowledge base.

I would like to have a future-proof idea of the cost and the roadmap for my class. This is in light of the fact that they are switching things up, promoting the cloud service and mixing different support levels.

The CMDB and knowledge platforms that are in the background of the ticketing tool should also be addressed. 

I have been using Jira for five years. 

When it comes to the question of stability, this depends wholly on the amount of resources provided to the virtual servers, since we make on-premises use. 

We have internal Atlassian experts, so it is tough for me to comment on the technical support.

The price of the solution could be lower.

We are currently in the initial stages of contemplating a switch from Jira. 

My advice is to work closely with Atlassian to make sure that all the designs are future-proof.

It is tough for me to Rate the solution. There are features needing improvement, but also many good things about Atlassian. As such, I rate Jira as a seven out of ten.