Jira Reviews

Its use case just depends on the company I've been with at the time. I have used it for defect management, development processes, and status. At one point, we ran our entire risk platform out of it as well.

The dynamic communication and the ability to customize it the way we want are the most valuable features.

Its ability to perform true executive-level status reporting could be improved. There are a lot of benefits there, but there are also a lot of things they can and should expand upon.

I have been using this solution for about eight years.

I have not interacted with them. I've struggled with getting Atlassian resources, but that could partially be my fault.

It depends on the type of license. In terms of subscription, it is cheap, and it works pretty well.

You need to investigate and understand dynamically what it is that you're looking to do. Don't just dive in and start creating. Before going into it, you should really organize your formatting or direction of the cause. There are other tools that are like cookie-cutters. Jira is so customizable that you really need to define what you're going to do with it.

I would rate it a nine out of ten.

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. 

We are using Jira mostly for the workflow dashboards for our projects. For example, for now, we are using the Kanban boards at team levels and also between team cooperation levels.

The links between tickets are very valuable and the boards I found to be configurable and usable.  The boards allow some level of extended configuration and they can be customized according to our project needs. Additionally, it is easy to use.

I'm mostly focusing on the requirements traceability with my thesis, the integration could improve for other tools. The companies are not only using Jira. For example, for the test cases or for the documents templates, we are using Polarion and we have been having some integration issues.

I have been using Jira for approximately four years.

Jira is easy to scale. We are implementing it for our team and for other teams, such as the relations teams. If you look at the different levels, such as the coordination levels, we are using it extensively on a daily basis.

In my team, we have less than 100 users using this solution but we also have other teams in our large company that could be using the solution. Our company has thousands of employees.

I have not contacted support.

The initial setup of Jira is straightforward.

We have a team in my organization that specifically handles the support of Jira.

The stability and performance are good, I have not had any complaints from people using Jira.

I would recommend Jira to others.

I have not used many tools to compare Jira with.

I rate Jira a seven out of ten.

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. 

We use Jira to create releases, tasks, sprints, and collaborate within teams. The solution can be deployed on both the cloud or on-premise.

Jira has a useful user interface and overall is easy to understand and learn.

Performance is something that can always be improved upon in a feature release. Additionally, it would be a benefit to add Markdown in Jira because sometimes it might be better to describe everything in Markdown because it is a common language structure.

I have been using Jira for approximately eight years.

Jira's stability could improve. We have experienced times when we were out of memory which is possible due to a memory leak. It is hard to pinpoint the cause, it could be the operating system.

I have had to contact the support when I had some questions about the upgrading process and they answered in a timely manner.

I have previously used a comparable solution to Jira and the largest benefit was it was free.

The setup is not difficult. I have done it a few times in Kubernetes and did upgrades, the experience was straightforward.

There are other solutions that are free making this solution seem expensive in comparison.

I have found the cloud deployment better than the on-premise. However, for those wanting to implement this solution, I would advise them to compare the pros and cons of each before making their selection.

I rate Jira a ten out of ten.

We have been using Jira for schedule management as well as for making updates to our projects. I mention this in my capacity as a project manager. I most recently used the solution this year and did so for scheduled management of our varied tasks and projects. JIRA is actually used to put together an entire portfolio for each one of the teams, meaning for everybody. The solution listed each of our projects individually, with us needing to provide daily and regular updates. 

A most valuable feature involves the ability to customize the entries and to update them quickly. Unlike what was previously available, the solution allows us to create specific codes and symbols for the individual teams. The new version allows one to customize and to use demarcators. There is a code that can be entered in Align upon completion of a project or task and this apprises the project manager that it is time for its removal. 

Something I do not like about the new version is that there is a need to browse all the way back to the beginning, should a person click on a task that is specifically for his group and wish to go back and look at the other portfolios or people. However, I cannot state definitively if this situation owes itself to the way our team put the site together or to something administrative. When clicking the back button it would take the person to the wrong page, not to the one he desires. One would actually have no choice but to browse back to the portfolio and to find his group again and open it. Again, it is not clear to me if this problem lies with Jira or with the way our team laid out the site. 

I feel Jira is stable. The only hiccup which comes to mind is the one I mentioned, although it is not clear to me if this owed itself to the network we were using or to limitations of the application. Except for this, everything about the solution is stable. The only time a person can not look at the information is when the administrator announces his intention to remove it. 

The scalability is pretty good and we started on this process from the moment we started utilizing the solution. While we had only three teams and three sections, between December and January 15th the developers came together and expanded from three to 76 different tasks across the different teams. By February there were over 300 teams. Expansion is easy and did not just encompass our teams but also provided links to others that were outside of our main team set so that there were reference points available.

I would say the tech support is pretty good. I got back a couple of answers in response to an email I sent out. 

It was quite easy for me to set up my own pages. I had a field day with creating my own test pages and was able to play around with them and simply test out the different settings. Pulling in new documentation was very easy. The same holds true with pulling in attachments and it was, consequently, easy to set up. As well, I was able to set up certain sub-pages for our team for going in and checking JIRA.

There were initially eight people involved in the maintenance of the solution and deployment of updates. They had the people to whom they answered. We are talking about a large-scale effort. Without taking into account the Jira support line, I would say there were around 12 people managing and administering this version. For our specific team, there were around three. They were the actual decision makers. 

I am not in a position to comment on licensing costs. 

Our team does not use the solution exclusively. There are multiple ones which do, although I cannot state how many teams are doing so. I do know that the entire section of our agency is doing so and this accounts for a lot of people, well over a hundred. 

The solution is pretty good and is geared towards those with multiple teams who are using it for the same purposes as us. We use it for providing daily and scrub updates, for which it is really good, as it allows one to track every entry and see when it's entered, timestamp and all. So, if a person has a lot of mission-critical or time-sensitive activities, JIRA is pretty good for tracking and helping to keep everything organized.

While I am still biased towards services at the moment, I rate Jira as an eight out of ten, at it is really good and very functional. 

We are basically using it to register all the requirements and issues so that we can track them and control the flow and different states. We also use it for reporting and configuring dashboards for portfolio management.

It is a SaaS solution, and we are using its latest version.

The flexibility to create different flows is most valuable.

It can have a more high-level view of portfolios. It has quite detailed views, but I would like a high-level view of portfolios.

We want to integrate Jira with Microsoft Active Directory, and I don't know how easy or hard it is going to be. I don't know if Jira supports this. We are starting that integration in the last quarter of this year. I hope to find all the required tools for this integration.

I have been using this solution for two years.

Its stability is very good. I have no complaints.

It is scalable because it is a SaaS solution. It is the best choice for us because it responds to our needs all the time.

We have around 100 people in our organization who use this solution. They are developers, QAs, and managers.

Their support was very good for some of our questions. We didn't have too many issues.

We also have a partner who helps us with all the contracts, payments, and other things. If there is an issue, we contact them, and they provide support.

It was easy because the person who helped with portfolio management had previous experience with Jira. So, it was easy for us. It took about three weeks.

The most important thing is to precisely decide your flows and different stages and cycles. If all these are very clear, you won't have a problem setting up Jira.

I would rate Jira a nine out of ten.