Jira Reviews

Jira is used for issue tracking and defining the development pipeline. It's helpful to define when a project is done and track a task as it moves through different stages. The deployment type varies based on the customer's environment. We sometimes connect to the client's setup, which can be in the cloud or on-premise. 

I like that Jira allows you to customize the flow for an agile process and adapt it to your own flow.

We've used Jira for around 10 years.

We evaluated Jira for security and stability, and everything went well. 

Jira performs well and scales up enough to meet our needs. We probably have about 200 users, so we don't need more than what it offers. 

We used a solution called Mantis a long time ago. We're a software outsourcing company, so we adapt to our clients' setup. Plus, Jira serves our needs well, so it made sense for us to work with that. We don't recommend anything else. We use Azure DevOps, Jira, and Confluence on our projects. If it's not in Microsoft, then it's Jira and Confluence.

Deployment isn't something I handle personally. Our DevOps department does that, or it's installed by the client, so I'm not dealing with it either way. One engineer is enough to deploy.

I don't know the price of all the setups. Our clients pay for the setup, so our Jira users are covered by them. Of course, the price could always be cheaper.

I rate Jira nine out of 10.

We use Jira for software development and issue tracking, enhancement requests, and software lifecycle management.

Jira has benefited the organization because it's necessary for doing our job well. We would need to have Jira or a similar tool. For example, it's could be similar to working with documents, you need Word or a similar tool.

The most valuable features of Jira are all the integrations with other systems. It's not the best in any specific area but it has lots of plug-ins and integrations.

Jira could improve the workflow, screen, and field configurability. They are lagging behind other solutions, such as Allegra in work system configurability.

It depends on your usage pattern because if it's more configurable, you can configure it to be a very different kind of tool which is a benefit.

I have been using Jira for approximately 10 years.

The performance is not very good for Jira but the reliability is good.

Jira can handle a lot of tasks. In my project, we have approximately 50,000 issues to be resolved and it worked well. However, the overall solution is slow.

We have approximately 25 employees using Jira in my organization of a total of 2,000 employees.

I use Jira moderately while other of my colleagues use it daily.

I have not used the support from Jira.

I have been using Allegra previously.

I was not around for the initial setup. However, I tried to configure it later and it is not easy. It is not as easy as it should be.

The solution is on the cloud, there is minimal maintenance.

The price of Jira is reasonable.

My advice to others thinking about implementing Jira is if you only want it for the standard flows and use it as an issue tracker in a software development setting, it is a good solution. We are using the online version. If you are in need of changing workflows or appearance, fields, screens, et cetera, Jira is not able to do this well or it's not possible at all.

Jira has found its place in our organization and it does those tasks. They should focus on speed and stability, and in that order. It's excellent with regards to preexisting integrations but it is poor at configurability.

Whether Jira is a good solution for you depends on your use case. From what I have seen creating different workflows in Jira is not good.

I rate Jira a five out of five.

We are using Jira for user requirements, our development, and for our agile and scrum requirements. We create scrum boards for our projects.

The most valuable feature of Jira is the project package for development.

I have been using Jira for approximately three years.

 JIRA is very stable.

Jira has the ability to expand it is scalable.

We have approximately 25 users using this solution in my organization.

The technical support has been very good.

The initial implementation of Jira is not difficult because the solution is on the cloud.

The price of the solution could be less expensive. We pay annually for the solution.

The solution is very good and there is not much to improve. This has been working well. Our teams have been happily using it.

I rate Jira an eight out of ten.

We have really noticed an improvement in the way we work.

It's a really good product. I feel it really changed the way we work and at this time we're not looking to move to another platform.

The features on offer are great. It has everything we need.

The solution needs more integrations with Azure DevOps OnPrem.

I can't speak to any missing features. It has what we need overall. 

Company-wide we started using Jira this year, however, I've been using it since last year. The company hasn't used it for that long.

We aren't looking for another solution at this time. We're happy with Jira. 

As far as I know, we are just a customer. We don't have a partnership or anything with Jira.

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

Some of the use cases are for tracking issues and bugs.

I am responsible for an administering job for Atlassian Jira at my company. I'm working for some of the major IT companies in Kazakhstan.

The solution is deployed on-premises.

The solution is valuable because it's pretty flexible. It allows you to do a lot of stuff, and the functionality is pretty rich. It integrates well with other products, like GitLab, that we are currently intensely using at the company.

The solution could be more user-friendly.

I have been working with Jira within the past year.

The solution is pretty stable.

The solution is scalable. There are a few dozen users using this solution. We might increase the usage in the future.

I previously worked with ClickUp and would suggest using it. It's a competitor to Atlassian Jira.

When it comes to functionality and usability, I think ClickUp is better, but compared to Jira, ClickUp's drawback is their integrations with other products. The product is not old enough to be mature.

Jira is more flexible and more integrative with other products, and ClickUp is more user-friendly. The functionality is pretty rich.

I would rate this solution 9 out of 10. 

The only thing that I'd like to advise is to just monitor the market and keep an eye on comparison between the Jira and ClickUp.

We use Jira as a help desk, an IDSM. We use it on a daily basis. Every ticket gets opened on it.

It's very simple to change the workflow and adapt it. Jira is very user friendly for the agent and the user.

It's a very customizable solution, but as a customer, we're always looking for additional customization. There could be better customization in future releases. If we changed from Atlassian to another product, we would look for a customizable solution.

I have been using this solution for many years.

The stability of Jira is good. We haven't had any issues with stability or performance.

It's a license-based software, so if you pay more for the license, the solution becomes more scalable.

Customer support is usually good. I have had no issues with them. 

Setup was straightforward. There is no dedicated team for maintenance. Our IT department handles that. It's a simple solution.

There are no additional costs to the standard licensing.

I would rate this solution 10 out of 10. I recommend Jira. For the time being, everything is good. Their support is good. The platform is good. There are no issues with them on any level. We mainly picked Jira because of its stability, integration, and price. If a solution is well integrated in our environment, and it's not costly, why not configure it?

The biggest thing I have taken away from working with Jira is that it's very simple.

Our company is a consulting company and then we are an Atlassian partner as well. Therefore we use many functions of Jira. It's sometimes project management and sometimes to communicate to outside customers.

The solution is very fast.

It's a very useful tool. Jira is very useful for project management for internal projects. 

We can easily communicate with many things easily in Jira.

There's the ability to easily customize the product. There's lots of great potential functionality.

The solution is stable.

You can scale the product very well.

We'd like to see more collaboration tools implemented within the product itself. 

The product needs to allow for more communication between individuals and teams. 

The solution could always use better reporting. 

I've been using the solution for four or five years. 

The solution is very stable. There are no bugs or glitches. it doesn't crash or freeze. 

This is the type of tool that would work well for any size of organization, from a smaller company to a very large enterprise. 

The product is very easy to scale and extend the user license. In terms of functional expansion, for projects, it's very easy to expand. You can do so in no time. It's very quick.

For the most part, we are satisfied with technical support. Sometimes in some areas, if you find a bug on Atlassian, they respond quickly. However, sometimes, they are slower. It can really vary. For the most part, they really try to get to things quickly. 

The initial setup is different and is case by case, however, for a single person or scrum team, it's not too hard. The process is simpler on smaller setups. The more processes the company needs, the more complicated the solution gets during implementation. 

We have our own engineer team internally that handles maintenance. We have no problem with maintenance tasks. It's not too hard to handle. 

We provide implementation services to our customers.

Jira pricing is very difficult to pin down. They stopped another licensing version earlier in the year, in February. Now they have only data center licenses and then cloud licenses. These are more expensive than a server license. With a server license, you pay once. When you get a cloud license, it's an ongoing annual cost. We would have preferred if the old licensing model was kept.

We are Atlassian partners. 

We are using the current version, the latest version right now.

We use both cloud or on-premises deployment models. It's a hybrid approach.

I'd rate the solution at a nine out of ten. I'd recommend the product to other users. 

We primarily use the solution for our own projects.

The solution, for the most part, offers good usability.

The ordinary user has an interface that is very clear.

It's very easy to collaborate, especially on-site when there are a lot of moving pieces. It's a great collaboration tool.

Some of the interfaces, especially on the administrator side and for permissions, are not so clear. They aren't very user-friendly.

For admin to get permissions and stuff like that for their members it's a little confusing sometimes. That said, the rest is very clear.

The integration of what we call "Issues" in Jira could be better. The Issues integration with Bitbucket Pipelines could be better. If Jira can provide an easier way to configure and use this functionality, that will be helpful for workers.

I've been using Jira for more than ten years now. It's been a while at this point. 

I looked at other options, however, Jira is so famous and well known that I did not have to look for other software.

We are a customer and an end-user. We use Jira for internal projects. I'm a Java architect.

I'd rate the solution at a ten out of ten. I'm very satisfied with its capabilities.