Jira Reviews

We use Jira for project management.

Our team really needed something to help us track the progress that is made against our system-level requirements, and this solution helps us in that regard.

The most valuable feature is Jira Align, which is a plugin that helps you to understand the progress that is made against each epic. I have had limited exposure to it but by using Align, we can also see the progress concerning Initiatives, including progress made against the requirements.

In general, Jira Align is very useful for management. It allows them to see the big picture and what is really happening from a team-execution point of view. Being able to see progress against their Initiatives is a nice feature.

The UI is good, and it helps us to see what needs to be done to complete our sprints.

Nowadays, many organizations are moving toward the Objectives and Key Results (OKR) framework, and this is something that Jira should be able to accommodate. Jira should understand that at the leadership level in an organization, such as the C-level or even below that, they don't like to have an epic creator. Rather, they are interested in observing all of the corporate objectives that are being turned out by the team.

OKR is a very important feature for them to add, and it's a big investment. There are separate tools that are trying to support and enable people to use this framework. If Jira could do that, it would be great because we don't want to integrate multiple tools. For example, we don't want to use one for OKR and another one for Agile backlog items. If we can have support for everything using one tool, it would be helpful. That said, it would require a big investment to implement.

The biggest drawback that Jira has is that they don't have a separate chart to show metrics for lead time, cycle time, and throughput. We use the control chart as a workaround but it's not giving us the correct metrics. The metrics are skewed because the chart shows us some items that are still in an open state. This is something that needs to be fixed. By comparison, Rally Software has a feature that enables people to understand the lead time, cycle time, and throughput as separate metrics in different charts. Having Jira implement that capability would be helpful.

We are unable to enter an explicit agreement below the kanban board, which is something that we would like to be able to do.

I have more than five years of experience with Jira.

Stability-wise, Jira is good.

Jira has no problem with scalability. It's far better if you compare it to Rally.

I also use Rally Software. Some times are more on Rally, whereas other things are more on Jira.

Rally software has some better charting features, whereas Jira is more scalable.

Between these two products, it's very difficult to say which I would recommend. Rally has some good features that are not available in Jira. For example, in Jira, we can't put an explicit agreement below the kanban board. This is something that we can do in Rally. Rally Software, on the other hand, does not have the feature that allows us to understand the progress made at the feature level or the initiative level. This is something that Jira gives us with the Align plugin.

I would lean toward Jira as the market leader. If they improved some features, such as the metrics available on the charts and support for OKR, I would prefer and recommend it over Rally and other products.

The pricing for Jira is reasonable, although I think they can bring it down because the plugins cost extra. Jira Align, for example, is available at an additional charge.

Jira should understand that there are now competitors in the market, and they should lower their prices to expand the user base. As sales volumes increase, the price should naturally be brought down. In this case, people are more likely to retain their licenses instead of switching to a more cost-effective solution.

I would rate this solution an eight out of ten.

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 Agile Practices, so we track all our projects in Jira. When the project starts, we start putting all the user stories there. If any user story has any down the line task or user career task, we attach those Jira stories to our Confluence pages as well. So we maintain Confluence pages as well as Jira together as a story. The requirement and the Jira story are linked together.

Managing and keeping track of projects is a little bit difficult in the IT world. Jira provides the exact picture of where a project stands. It also provides automation or DevOps technologies. This brings our company together, and whenever we have to see a project's exact state, we can use Jira.

It's a Scrum tool, so it's very easy to use. That's what I like about it.

You can very quickly create a new project, add stories, and then make them into a sprint. It's very user-friendly.

Jira covers everything for project management and life cycle related items. It's a fine tool to work with.

I have not seen any issues with stability or scalability.

Sometimes, it gets a little bit difficult to find the exact issues for people, but the search works fine in general.

The Classic UI is a little bit messy. UX experience is also a little bit messy and is not according to the expectation of a tech user.

If I click on an issue, that issue opens on the side. It shouldn't be like that; either it should open as a pop-up so that I can see where it is opening or it should open somewhere else, maybe as a pop-up or a new page. The view on the side is a bit of a hurdle. The UX needs to be improved.

Good use of Kanban technology should be there. Right now, it is mixed with Scrum technology, but that's not very necessary.

I've worked with Jira for more than five years. Our company has been using JIRA for a long time.

It is stable; I've never seen it down.

The scalability is also good. We are a company of more than 800 people, and I haven't seen any scalability problems as of yet.

Most of the users are developers, and at least 700 users must be using Jira in our system.

I think the starter pack of three users, up to five users, is free. So you can try it out.

In terms of project management and repository management for the code, I find Jira to be the best. So on a scale from one to ten, I would rate it at nine.

We use Jira for task tracking, sprint planning, and backlog.

The dashboards are useful. You have visibility across projects and various dashboards.

The status of the different activities is also helpful 

In general, it is not user-friendly. 

For a non-technical person to use, Jira is not intuitive. If you are a developer it's fine, but we are trying to get other technical people in to look at tasks or to update a task, move it from one sprint to another sprint and it takes more effort than I would like.

I would just like to see it easier to use, and I would like the workflows to be less complex to do what we need them to do.

My experience with Jira is limited, but the organization has been using Jira for three years.

We are using the latest version.

Jira is stable. to my knowledge, we have not had any issues with bugs or glitches.

The scalability can be complex if you are using workflows.

We have approximately 20 developers and some managers in our organization who use Jira. 

I have not yet used Jira technical support.

Previously, we did not use another solution. We started with Jira.

Along with Jira, we use Microsoft Azure DevOps.

The initial setup is fairly straightforward. 

It was fairly simple for us.

I would recommend getting sound knowledge first. It is difficult to go back later to fix things, so try to build it right the first time.

For the functionality that exists, I think that it's good.

I would rate Jira an eight out of ten.