Jira Reviews

We are using Jira for ticket management.

The solution has helped my companies efficiency with managing tickets throughout the life cycle.

We have gone through several version changes and some of those changes have not been intuitive. There was a learning curve and we had some complaints internally about the changes, such as the new interface.

The solution could improve the Agile reports. They do have quite a bit of reports already, but additional reports would be a benefit.

I have used Jira within the past 12 months.

Jira is stable.

I have found Jira to be scalable.

We have a few hundreds using Jira in my organization. They consist of developers, project managers, and testers.

Whether we increase usage of the solution depends on what each team wants to do. There is some level of common solution approach, but I don't know for sure whether this is the direction that everybody is wanting to adopt.

We had to reach out to their support a few times. The support was good, I did not have any issues with them.

The initial setup was not difficult.

We have an IT team that supports the solution.

My advice to others wanting to implement this solution is to utilize the SaaS solution unless it is required not to. Having your own instance running in your data center or private cloud requires your own staff and resources to maintain and upkeep. It can be quite time-consuming work. Unless you are invested in something like that, there is a benefit of just using a SaaS solution.

I rate Jira a seven out of ten.

Public Cloud

I'm from a QA background and we used to do automation. It was far easier to link JIRA with our QA automation frameworks because JIRA has a lot of public APIs that we could use. Also, the burndown charts and the ability to manage different frameworks of the adjoint model are helpful. We could use scrum in one project or Kanban. So it was easy to manage the transition from one framework to another. Those are the things I found useful, but I haven't seen the case of TFS yet.

JIRA could simplify the query mechanism. Running a query for tasks, stories, and so on is far easier in TFS. The algorithm is easier. In JIRA, it's a bit complex in terms of what advanced search queries we use. Sharing them is also a problem. Because TFS is on the cloud, we can easily save that query and share it with our team members. So that is one area where JIRA has some room for improvement.

JIRA is pretty much stable.

JIRA is far more scalable in terms of using different frameworks, burndown charts, dashboards, etc. The size of your company doesn't matter. JIRA has the capability to work for smaller organizations and larger ones as well.

JIRA's technical support is absolutely fantabulous. I had used it in the past when I was working at my previous organization. And when we wanted to link it with a framework, they helped us out with the API we were looking for. There were certain areas where we were looking for a specific API. And also they have a lot of options in terms of packages that you can choose according to your company's needs. They had custom packages available. You do not have to buy a larger package. They have smaller packages for smaller organizations. So that's something exciting.

JIRA is fairly easy to set up. That is not a problem.

JIRA's pricing is very economical. I would say that JIRA is a great deal more economical than Microsoft. So pricing-wise, JIRA is also good.

I would rate JIRA nine out of 10. From a technical background, it depends on what you would like to use — which stack you want to go for. In other words, it depends upon the kind of infrastructure you have right now. For example, say you are developing software on Microsoft's .Net framework, then you are obviously already using Visual Studio and Microsoft Stack. In that case, it's a lot easier to integrate with TFS. But if you are using open-source solutions, like a Java platform, you can go for JIRA. So it totally depends upon the technical capability, or technical infrastructure one has.

I primarily use the solution for use cases and make sure that our tasks and priorities are getting done.

I like that we can actually categorize the stuff from high priority to a lower priority. You can make categories and you can focus on the right items that need to be worked on. 

The initial setup isn't too complicated. 

The solution is stable. 

The scalability is good. 

It is not intuitive. It was hard for me to understand how to use it right away. It would be ideal if they could make the solution more user-friendly so that it is easier to pick up.

I haven't been using the solution for that long just yet. it's been about six months or so.

There are no bugs or glitches. It doesn't crash or freeze. it's reliable and the performance is good. 

The solution can scale well. it's pretty straightforward if you need to do so.

We have product owners, project managers, and scrum masters on the solution. I would say that we have a thousand people using it, however, I'm not saying that for sure, as the bank has 46,000 employees and I'm just a part of a small team. I'm estimating that I would expect over a thousand people to use it.

I have never used technical support. I've been able to manage everything and figure stuff out with the stuff I have here. Everything is available to me.

I did use a different solution, however, I switched when I switched roles at the company.

For the most part, the solution was set up for us. My understanding is that it was pretty simple I assisted a bit, and I found that the navigation piece was not enjoyable to implement. 

I'm not sure which version of the solution we're using currently. 

I'm a customer and an end-user.

I'd advise users considering the solution to make sure that they have a little time to review it and understand the tool and make sure they actually find that it is a good solution to meet their needs and that it's what they're looking for. From Agile delivery teams that are here to deliver their MVPs and stuff like that, I think it's great to keep track of all their backlogs and stuff like that. It is also great for someone from a use case perspective as they break it down well.

I'd rate the solution at an eight out of ten. Of course, I'm still learning it. That said, it's great for keeping track of all the items and the stuff that needs to be done and for the use cases that have been closed, to make sure that we get the proper sign-off and understand the line of business. 

Public Cloud

In terms of using Jira, I was more on the user side and not really acting as, for example, service desk or support for the Jira installation. That was not my part of the project. I was more tasked with setting up the infrastructure from the architecture point of view. We needed a ticketing system and we need a planning system and the team that was responsible for the tools was installing and providing them with the workflow that we needed.

The solution is pretty flexible. I have worked in different projects using different features. From agile to just normal project management and task management. It's got a lot of great features. 

If we're talking specifically about project management, the solution is pretty nice. There are a bunch of modules and plugins and add-ons that you can use if you need to.

The test management aspect of Jira is pretty pure. They have a lot of great plugins that really expand your options.

There's always room for improvement, however, it depends on how you intend to use the solution. It's hard to pinpoint exact features that are lacking as the solution is quite vast.

From the project management perspective, I would say there are a lot of different issues that could be tweaked. There can be small improvements with traceability, for example.

I have no idea how long I've been working with the product at this point. It's probably been about ten years or so.

The pricing is fair. Right now, I'm using the solution for my small projects. For example, I'm using the Jira Cloud and Confluence Cloud, which are pretty nice. For small teams, it's a very, very interesting option.

We're just a customer.

I'd advise, for those users who don't need an enterprise-level environment, that they go for a cloud deployment. For others, they don't really have a choice. They will have to follow up with enterprise security and other protocols. There are not that many options, I would say. 

I have learned that Jira, starting in 2024, will not be available as a server installation anymore. Soon there won't be any options at all. It will be the cloud or nothing. 

Overall, I'd rate the solution ten out of ten. It's a very good product.

For small teams, the cloud works well. You can do basically whatever you want there, so it's fine. It's also not cost intensive if you're talking about using it for small teams.

I am a consultant, and we have some customers with projects who use Jira.

We have customers with different Jira installations because there are so many vendors. It is mostly used as a bug tracking system with tickets, issues and tags.

The feature that I have found most valuable is that it is a quite powerful user tracking system. Also, we use it to print tasks for planning so you can also see what's happening in the system and follow the tickets.

In terms of what could be improved, there is not much I don't like. It is a little bit faster but with Firefox it can be slow, but that is also the case with many other tools as well. It has quite a lot of options and fields, so I'm not too familiar with them all. That makes it a bit trickier. It could be a little bit easier, it is not that simple or straightforward. 

The tool itself is so powerful and the customer's expectation is very high because you have so many things you can do with it. That can make it a little non-user friendly.

I would want to see Jira include some improvements, like drag and drop and color, to make it more straightforward. If you compare it to Microsoft or Octane, they have good features that I would like to see in Jira as well.

Overall, Jira is a little bit old fashioned, it could be more user friendly.

They should make it simpler, to just be able to do some functions, whereas now it takes longer. There are too many clicks.

I have been using Jira for around 15 years or so, but not all the time.

The stability is fine. We have some issue now with our customers, it could be due to the network or other issues, I don't know if it is because of Jira itself. We have quite a complex environment and system for our customers. At the moment we have several tools and different systems. We have some issues with downtime but I am not sure why.

My advice to anyone thinking about Jira is that it would be wise to at least find out the most crucial functions that you need in the product, what features are most important, determine how the project will use Jira, and the most important thing is to have some kind of user training plan because the tool is so complex and flexible that you can use it in many, many different ways. 

On a scale of one to ten, I would give Jira a nine.

I would give it a nine because of course it needs some improvements. For example, the usability and its speed.

On-premises

The adaptability of the Scrum and Kanban boards for other uses, with careful use of the customization features.

It has simplified our PM work tremendously, as we switched from VersionOne. We have much more buy-in from dev teams and we see a marked difference in productivity.

Ease of administration and customization. It is really clunky in this area. Also, permissions are nice, but they need more refinement so a project admin has more capability and less reliance on the system administrators.

We have been using this solution for approximately four years.

There were issues with deployment. Because we use it on-premises rather than in the cloud, for regulatory reasons, we are often behind, but not for long. Apart from that, our PlatOps team always runs into problems, though I cannot speak directly to those issues.

There weren't terrible issues with stability, but it is easy, when customizing, to make a mistake that will "break" JIRA for all users. It takes a lot of care.

I did not encounter any issues with scalability.

Customer Service:

Customer service is excellent, although they are only available via email.

Technical Support:

Technical support is excellent, because they are responsive.

We used VersionOne and it was simply too powerful, so to speak. It was bulky, expensive, and simply became a mess with so many users. VersionOne isn't a bad product at all, but our IT department just isn't big or complex enough for an "enterprise" product.

We implemented it ourselves.

Our ROI is very good. Almost all licenses are taken and it is even being used by the rest of the business, outside of IT.

The licensing model is annoying. They nickel and dime you.

We evaluated Asana and even Trello, as we were trying to simplify. But those solutions, among others, were too simple.

Ensure that your admins learn by first installing to a QA server for experimentation, if you are doing it on-premises. As for those learning it in the cloud version, create dummy projects, categorize them as such, and be careful about how many changes you make at once.

Getting our Service Desk out of a system of stored emails and into a ticket system where we can queue, assign, track, report, and store knowledge has been great for us.

JIRA was our first experience with ITSM implementation. It allowed us to reduce the amount of tools we were using, standardize our procedures, and measure our work. This allowed us to show the need for additional staff resources, additional training, track our busiest times and prepare for them.

Administration: JIRA administration is not as efficient as it should be. JIRA is aware of many relationships but doesn't bother to show them to you on the admin side. Example. JIRA knows what roles I'm using for a project because they are listed in the permission scheme. Rather than just showing me the roles listed in the scheme it will show you every role in the database. This makes the page load slowly and is frustrating to scroll through. There are many other examples of this same function for administrators.

31 months

No, deploying JIRA in our VM environment was not a problem.

We did have some issues with stability in the beginning. We were pushing the ticket limit is 4.1 and it caused some issues. We later tested the High Availability Clustering and the archival tools for this which were very nice and did work, but were to expensive at the time.

We did have some limitations but that was not an issue after 4.4 when the ticket limit was doubled.

Customer Service: Customer service has not been helpful but I have not minded since the wiki documentation and Atlassian Answers forum have been great. The developers I have done beta testing for have also been great. They are good about using your feedback as they design.Technical Support: The wiki and forums are wonderful. I get all my answers from those two sources. Talking to a customer representative has not led to anything useful.

We had a system called EPIC that we had created in house and did not have the functions and capabilities JIRA had. JIRA was also a more cost effective solution.

I did have complexities in the beginning and again as I was scaling but they were not the tool as much as establishing efficient shared processes and procedures.

In-house. Two of use spent time learning the tool and implementing it in our area first and then across the University.

In dollars, nothing. We are not charging to use our implementation. In employee resources, project planning, training, staffing, process efficiency, a lot. It would be hard to say the actual cost.

Our original cost was about $2000 for our licenses and hosting costs to get started. We are currently paying about $6000 dollars per year for our current installation.

We tested three or four other options including, BaseCamp, Footprints, Drupal, and a lite version of BMC. We were a small area at the time and JIRA's combination of cost model and function won.

This is a very cost effective application if you are looking to do application development, incident management, request fulfillment, problem management, knowledge management, or project tracking at a low maturity.

We use Jira mostly for task coordination and assignment. Additionally, scrum methodologies defined work items and bug issues. If we create any bugs all of them are fixed.

Jira can improve by making methodologies better, such as scrum and agile. Additionally, improvements in Kanban boards are needed.

I have been using Jira for approximately five years.

The stability of Jira is good.

Jira is scalable, this is in part because in our company we use it on the cloud.

We have not needed to use the support from Jira. It is easy to find information on Google or any other search platform. If we encounter an issue we can find the solution online.

The initial setup of Jira was simple.

The standard package of Jira is for 100 users. They should offer more packages for other increments, such as 500 or 2,000. In my previous company, there was a free package that provided a minimal number of users.

I rate Jira an eight out of ten.