Jira Reviews

This solution focuses on lean methodology which we have found useful and it can also be used on any device. 

In Jira Code, you can create workflows easily and distribute them within different departments. The user interface is easy to use. This is a simple solution for a new business that is not familiar with technology.

Jira's collaboration and integration with other apps and tools could be improved.

Jira does not focus on ITSM documentation and procedures. It is more advanced in user-friendly workflows but is missing the functionality of artificial intelligence AI which could be embedded in the ASM management.

I have used this solution for six years.

We are using the on premises solution which is very stable. There is a team that is currently working on its performance tuning. This solution is suitable for mid-sized companies.

Jira, compared to other market leaders like ServiceNow, provides a lot of features but focuses on service management only. I would rate it a three out of 5 for scalability. 

We have not had any issues with Jira support. There is an online knowledge base and a growing online community which helps with troubleshooting. 

The initial deployment was straightforward.

We implemented this solution internally. 

The licensing model for enterprise users is costly. We have more than 2000 users and it is becoming expensive to use.

I would rate this solution an eight out of ten. 

Our organization is a software development company. We serve financial institutes that have between 8,000 and 13,000 employees.

We use Jira for process automation and as a workflow engine on the client's side. For example, a customer can fill out a form and ask a question, which is operated by Jira, and someone will be prompted to contact you with the answer. We created the forms designer and the roof engine and handle the process with the customer contact.

We are using Jira for automatic tools, so it is run on-premise.

The most valuable feature is that it has different APIs available, with good services, and it is completely by the books.

Jira could improve the documents management level. Our customers compare it to Office 365 and Sharepoint Online. They are focused on versioning of the document; Jira is missing this in their environment. It is missing functions for collaboration, like instant messaging. Currently, we try to connect the systems, we use Jira workflow which is connected to Office 365. 

Jira is trying to push for the online version, however, our customers are not ready to do that due to safety concerns.

The features are not intuitive. It would be good if there were templates.

I have been using Jira for eight years.

Stability at the beginning had some troubles, but it is okay now. To maintain a large network, we divide it between operations and development. We have approximately six people involved.

Jira is scalable.

The initial setup depends on the project. Smaller projects where we are using minimal functionality can be quite simple. On the other hand, we have a monthly deployment process where we extend the solution, which is a complicated process because it's running a system with a lot of users.

Pricing of licensing is too high.

From a user perspective, Jira is simple to understand if they use its data functionality. If you want to extend it to custom feeds then you need further education.

If you are considering Jira, take a look at the online versioning and online pricing.

I would rate Jira an 8 out of 10. 

I'm quite happy with it. 

The solution works well and does what it needs to do. It has been reliable.

The pricing of the product is fine.

We've never had an issue with technical support. We're happy with them.

I don't really have any areas for improvement. It works very well for what it is. I don't have any suggestions.

We'd like to see Jira have more integration with a development ID.

I've used Jira for six years at this point. It's been a while now. I don't use it as much as I used to, however, I still use it.

The solution works well for us. We don't have any issues with performance or reliability. There are no bugs or glitches. it doesn't crash or freeze. 

Technical support has been fine. We are satisfied with their level of attention and have been happy with them overall. 

We currently use Azure Boards, which is kind of a competitor to Jira, and one of the main reasons why is that it's more integrated with the development life cycle.

The pricing so far has been okay. I don't have much to comment on.

We're just a customer and an end-user.

I'd rate it as an eight out of ten. 

My primary use case is using the boards in working stories for freeing up the backlog and assigning tasks to my developer team. 

No other stats of graphics or reports from Jira are used. We use Grafana instead of that.

I really enjoy the easy way I can follow up the story's progress even when they are in progress or we test bug stories. When issues arise, they can play back to the team in order to fix all the bugs. They have a view of the backlogs in the current sprint and the next sprint. 

The initial setup is straightforward. 

There are many Jira add-ons available, however, we aren't using those yet.

The solution is stable.

We've found the scalability to be good.

I alternate Jira with Excel. I manage the progress of the stories in an Excel chart with dates on work progress or thing to do. I don't like the progress or the stage changing from the stories in Jira.

I've been using Jira for about four years. It's been a while. 

The stability is quite good. There are only some updates that are made by IT, however, it's working fine for me. I haven't dealt with bugs or glitches. it doesn't crash or freeze. 

The solution is scalable. I've tried other solutions, and this one seems to be the most adequate for my needs.

We have about 1,000 users worldwide. There are several projects running in several parts of the world. 

We do not plan to increase usage. We are using it as we need it and no more than that.

We've never faced any big issues and we have never had Jira go down. Therefore, we've never had a need to contact technical support. I can't speak to how helpful or responsive they are.

I found the initial setup to be pretty simple and straightforward. It was not an overly complex process. 

However, largely, we are just testing Jira. I can't speak to how long the deployment takes. 

I have three teams that can handle deployment tasks. There are six people in one, seven in another, and ten in the third one.

We do not use resellers or integrators to assist with the initial setup. We can handle the process ourselves.

I don't have any information in regards to the licensing or cost of the solution. It's not an aspect of Jira I handle. 

I have tried or tested other options such as Excel, Monday, Trello, Tetra. In comparison, for how I use it, Jira is the most adequate for my daily job.

We're a customer and an end-user.

Nowadays I'm using the web version of Jira for my client. I'm managing my boards, my sprints, and my backlog which are all working on Jira except the retrospectives. These are made in a code and not written down in Jira.

I would recommend the solution to others. It's easy to learn, easy to handle, and we've never experienced any downtime for a year and a half at least.

I would rate the solution at a nine out of ten. I haven't fully utilized the entire product, however, from what I have seen, it's exactly what we require. 

I use the solution for software project management and software lifecycles. Jira covers the entire process from requirement analysis to deployment. 

I prefer Azure DevOps and Microsoft Ecosystem to Jira. 

I consider Azure DevOps to be more user-friendly and to provide a better user experience. I feel Jira to be a bit difficult to work with. I specifically recall that i encountered difficulties with Jira when I wished to receive or generate a report. Azure DevOps offers a simpler and more user-friendly panel than Jira. Jira's reporting panel is not user-friendly and a bit on the difficult side. Azure DevOps also offers more options for generating queries and reports, especially when it comes to great dashboard visualization capabilities for the monitoring of one's project. This poses a big problem with Jira, as Azure DevOps does a better job of providing this feature. 

I find the dashboard to be Jira's most problematic feature. I do not like it and feel Jira is troublesome when it comes to visualizing the reports. These should be improved. 

Azure DevOps offers more simplified processes, maintenance and development than Jira. 

I used Jira for around one year, at which point I left my previous company and made use of it in the new one I joined, where I continued to do so. 

I find the solution to be stable, though a bit hard to use. 

We have not encountered difficulties with the scalability. 

We have had no issues with support. As with Azure DevOps, we take advantage of the open community and forums for resolving any issues which may arise. 

I prefer Azure DevOps and Microsoft Ecosystem to Jira.

I consider Azure DevOps to be more user friendly and to provide a better user experience. I feel Jira to be a bit difficult to work with. I specifically recall that i encountered difficulties with Jira when I wished to receive or generate a report. Azure DevOps offers a simpler and more user-friendly panel than Jira. Jira's reporting panel is not user-friendly and a bit on the difficult side. It also offers more options for generating queries and reports, especially when it comes to great dashboard visualization capabilities for the monitoring of one's project. This posed a big problem with Jira, as Azure DevOps does a better job of providing this feature.

I find the dashboard to be Jira's most problematic feature. I do not like it and feel Jira is problematic when it comes to visualizing the reports. These should be improved.

Azure DevOps offers a more simplified processes, maintenance and development than Jira.

As with Azure DevOps, we take advantage of the open community and forums for resolving any issues which may arise.

We make use of the solution free of charge. 

My recommendation, for sure, is that a person go with Azure DevOps. 

I rate Jira as a six out of ten. 

My primary use case of Jira is as our project management tool for monitoring and planning.

The most valuable features are the speed and especially the search capability - I don't think any other platform can compete on those.

The main area for improvement is the high cost of the product.

I've been working with Jira for two years.

There are some small issues with stability, like unexpected updates, but overall it's good.

I think you can scale Jira as far or as big as you want, it's very scalable.

Jira's technical support is easy to communicate with, and they are very responsive.

This product's cost is much higher compared to other platforms, but it's worth the extra cost. Some add-ons are only available at additional cost.

Jira is easier to configure than other platforms like DevOps. It's fairly easy to learn so long as you dedicate some time to it and is easier to use than other solutions. I would rate this solution as nine out of ten.

We are using it to organize most of our software development processes. 

Being a cloud solution, we usually have the latest version, but sometimes, we get a pop-up saying that there are some changes in a menu or some new features are there.

It covers most of the development process, and almost everyone uses it. We are using it for every role involved in the project, such as business owners, product owners, testers, developers, and DevOps. For example, the product owner defines a new feature, and then we take the feature and create stories and development, testing, or DevOps tasks. We then implement the new feature or changes to an existing feature. All the test cases and other things are in Jira. So, everything is done in Jira.

It is a very convenient tool. We can organize our sprints through scrum or kanban. There are scrum boards, and there are kanban boards. If you prefer scrum, you can use Jira. If you prefer kanban, you can still use Jira. You can create your kanban boards in a similar way as you create your scrum boards. It is very useful. It also seems to be very popular these days.

Its search and reporting can be improved. They are already nice, but they can be further improved.

I have been using this solution for more than 10 years.

Its availability is great.

We have different offices, and overall, there might be about 2,000 people. There are no issues with its performance or service. Almost all roles in our company are using this solution.

Other people have experience with Jira's technical support, and they are quite happy with their support. Personally, I never had a case where I needed any kind of support.

It is a cloud solution. It just requires licensing. Of course, some support would be required for all users of Jira, which could be in thousands. It might not be an easy task, but overall, I don't think a lot of time is spent on its maintenance and support. It is a very trustworthy service.

It is certainly a long-term solution for our company and for previous companies that I have worked for. They have these long-term term licenses, but I'm not sure if they really pay on a yearly basis. They are certainly using it for a really long period and for a lot of users.

I would definitely recommend this solution. It is very popular, and a lot of my colleagues have used it before. It doesn't require a lot of learning time. It is very good to use. I'm quite happy with the service. Of course, it can improve, but personally, I'm very happy with it.

I would definitely give it a good rating. I would rate it a nine out of 10.

The primary use cases for this solution are backlog management and sprint planning. Customers deploy this solution on-premises. 

The two features that have been most valuable have been backlog management and sprint planning and tracking. 

This solution could be improved by including a different model for the overall planning perspective. There's a Jira portfolio that we aren't using. The only challenge we're facing is that we cannot see the overall planning. 

I have been using Jira for almost three years now. 

This solution is stable. On-premises, the stability is okay, but when it's cloud-deployed, I think it will be more stable. 

This solution is scalable, but I think it will be more scalable when we go with a cloud deployment. 

I have never contacted support directly, but our team that takes care of maintenance, support, and customization connects with them. 

I previously used Micro Focus ALM Quality Center for around five years. 

Installation was done by someone else. For deployment and maintenance, we have a DevOps team of two or three. 

I implemented through an in-house team. 

We don't pay for licensing because we are using the Open Source version. 

I rate this solution an eight out of ten. I think it's much better than other competitors' products.