Jira Reviews

We use it for project tracking. We do software development. We implement software development lifecycle, and we use Bitbucket for CI/CD pipelines.

We have a lot of vendors operating on multiple projects, so in terms of operations, we need to maintain the backlogs of different projects. The sprint approach for roadmaps is cool in Jira, but we are looking at whether the same option is available in Azure DevOps because one of our clients is looking into using Azure DevOps.

Jira has a good reporting system. It also has an API, so we can do all sorts of reporting. 

There are a lot of things. A lot of features, such as time tracking, are only available through the marketplace. If multiple users are working on a user story, we aren't able to pull out the reports. So, there are many things that they aren't offering. They are available only through the marketplace. That's not good for a product.

I've been using this solution for five years.

It's stable. The stability on the cloud is 99%, but we have deployed it on a virtual machine. 

Both cloud and on-prem deployments are scalable. I'd rate it an eight out of ten in terms of scalability. 

Our clients are small and medium enterprises.

I'd rate it a nine out of ten.

Positive

The setup on the cloud is easy. I'd rate it a nine out of ten in terms of the ease of setup. The on-prem setup requires some work. I'd rate the on-prem setup a five out of ten in terms of the ease of setup.

We have four people who are working on Jira maintenance.

It's not very cheap. It's also not very costly. I'd rate it a five out of ten in terms of pricing.

I'd recommend it to others. Overall, I'd rate it an eight out of ten.

I use Jira for project management. I track all my projects through Jira, including the resources, the time, the deadlines, or the roadmap. For me, it's the tool to check the status of the project. If we have time to get more people on the team, we can use it to show the up-skilling and the availability of the team.

They offer 24/7 support.

It's easy to set up.

There's lots of documentation to help you learn about the solution and troubleshoot issues.

The stability has been great.

A company can scale Jira if it needs to. 

It includes by default all the necessary tools for a project manager to work and make their work more efficient.

The reporting tool and the approval tool need work. The basic reporting tool includes only a few basic reports. If you need an advanced report you need to download a specific plugin, install it, and customize your reports on it. Sometimes you need to know SQL, let's say, in order to get the reports. It's not user-friendly.

With the approval tool, it's complicated in order to create the flow in Jira in order to achieve the approval process among different people. That needs to be simplified.

I've been using Jira for almost now seven years. I have used Jira from 2015 until now.

It's a very stable solution; we've had no problems at all with that. There are no bugs or glitches. It doesn't crash. It's reliable. 

The product is quite scalable. If you want to expand it, you can. 

We have hundreds of people on the solution in our company currently.

I've used customer support in the past and have found them to be helpful and responsive. 

Positive

The initial setup is not complex. From what I understand, it's an easy setup and it's straightforward. They have a lot of user manuals as well, and they have also 24/7 support across different countries if you need help at any time.

While there is a cost associated with the solution, and licensing needed, it's not an aspect I deal with directly. 

I'm not sure which version I am currently using. the admin team handles the versions and updates. 

I'd advise new users to read the user manual first, before jumping in. They are really helpful and informative. 

I would rate the solution at a nine out of ten. It is one of the best tools that I have used. It's helped me a lot in my daily job. For me, it's the best tool in order to track teams and projects. 

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.

We use Jira to manage agile development from beginning to end. First of all, we lay out a backlog of everything that needs to be done. Within the backlog, We define a sprint of three to four weeks and prioritize in Jira. The backlog is stored and the sprints are defined in Jira.

The tasks or stories fall under the umbrella label "issues." The issues are created and assigned to developers, and the testing is tracked in Jira. After one is done, it moves into the QA stage. We track that all the way until we get to what is called "non-performance testing," which is part of production. We use Jira to track the status throughout, and we have daily stand-up meetings where all the developers get together to talk about their blockers, interdependencies, the net, etc. All of this is captured in Jira.

Our client is a bank, and we use a cloud version of Jira. We are the supplier, so we're onboarded and get a login for whatever they're using. Right now it's a cloud version that we are signed onto. They use a hybrid cloud because they have their own cloud because some of their systems are private, and some are in the public cloud. 

The bank works with a few cloud providers. They are using Google for this project. We are heavy into developing microservices, which use JKE, Google layer, Google Cloud Platform, Google Communities Engine, and all the other Google components for microservices development. Most of their stuff is deployed on Google, but they are also affiliated with a bigger bank that uses Azure, so some of their systems are deployed on Azure.

In terms of product management, Jira increases productivity and visibility into the product. Those are the top benefits this tool provides to the team. Also, it's accessible to the executives and whoever wants to sign on to Jira to see what's going on. 

There are different levels at which they can see the project. It depends on what they want. Somebody can, for example, create a report, but some of the reporting capabilities are not quite there. However, Jira can export all the data to a spreadsheet. Once it's in a spreadsheet, the sky's the limit.

Jira has a dashboard called Active Sprint. The board has a button on it for every developer, and when you click on it, you can see every task assigned to them along with the status. It's great to have visibility at that level. Every developer and test is there. 

Reporting is something Jira could work on. The reporting capabilities should have the same flexibility we see in Excel, including the ability to manipulate data and create graphs. They need to have that, so we don't need to export to a spreadsheet.

Jira should add some features from another Atlassian product called Confluence, which we use to track all the documents we need for development and testing. There should be better integration between Confluence and Jira. I like to use Confluence to do my reporting, and I should be able to go into Confluence and launch reporting at the source. 

Jira acts as a data source, and Confluence is where the dashboards are. It would be easy for Atlassian to develop all the dashboarding capabilities for executives so they don't need to log into Jira. There's too much there. It would be better if executives could log into Confluence, which is a document-based tool.

We've been using Jira for nearly three years, but I've only been directly using and trying to generate reports from it for probably two years. Before that, I had my project manager do everything with Jira, but lately I've been working with it directly. I might sign on and looking at things because I want to understand what's happening with the project. There are a few things that are not right with Jira though.

Jira's stability is pretty good. I haven't had any problems. 

We've never had an issue scaling up Jira for big teams. It's not a problem for the banks I work with or our in-house development.

I give Atlassian support eight on 10. 

Positive

I worked at IBM for many years, and we used an IBM product called CMVC. The difference is night and day. Jira is much better. 

Infrastructure is all set up for us, and we go back to the bank's infrastructure team if there's a problem.

I rate Jira eight out of 10. It boosts productivity tremendously by eliminating the chaos between development and QA. Jira manages the entire pipeline from development to production. If you're thinking about implementing Jira, you should go for it. It will make your life better by streamlining the tedious daily work of project management.

I am using Jira for some programming-driven planning and PI planning system, but I have just started using it for that. I am primarily using it for some projects.

I'm serving as an enterprise agile coach, so I work with a team to help them use Jira. I'm not really sure what the exact data subjects are, but I mostly look at what the team is doing and if they have updated, then they let me know. I'm not using Jira for my own instances, but for my team's. I'm helping the scrum masters and the product owners.

The solution is deployed on cloud.

In terms of scrum teams, I find that usually, the product backlog depends on charts and especially reports like Sprint Reports. I find the reports to be very useful. With regard to SAFe Agile, I was looking at having a proper program board. So far, I have tried using the portfolio feature. Something that I have been looking to understand or learn more about is how to integrate Scaled Agile and their work types into the Jira.

I'm still exploring the solution. I think the knowledge is a challenge because most people are used to Jira for teams, but not Scaled Agile. I think that is an issue with awareness. We are looking for some YouTube videos and help pages on finding that. Maybe there are features, but sometimes we aren't aware of them. We are still in the exploration stage.

I would love to see transparency in terms of how the program is displayed when you are working in multiple teams, especially how the dependencies could be tracked. The most important thing at the moment is that it is easy to do.

Something I would like to see improved is the traceability feature. When you have a user story, if you can see all the test cases, it would be an improvement if you could see any design documents or any change management. If you can see the traceability nicely, that is also something that we are looking for. Today we can link and do things like that, but sometimes the solution has a bit of a challenge with attaching test cases, so I think we have to use some plugin. Traceability with the test cases could be improved.

I have worked with this solution for five years.

The solution is stable.

I'm not able to comment on the scalability because I work with different types of teams. Some teams are really big, and they haven't said that they've faced any challenges. I haven't specifically asked, so I'm not very able to comment on that because I don't know for sure.

I'm working with a couple of teams made up of 20-30 users or 100-150 users, and maybe more for certain accounts.

I haven't had a lot of experience with technical support, but for the questions that I have raised, I received a pretty quick response, so I'm happy with that.

Setup wasn't that big of a challenge.

Implementation was done by Jira administrators, which was good.

The license is yearly. It is a large, long-running program.

Some of my teams have been using Version 1 and Rally. Because of that, I have been exposed to those tools for some extent.

My experience is much more with Jira. That's why I tend to go for Jira, but we haven't used many other solutions. Based on teams and what the people are saying, they find Jira to be more user-friendly. For Scaled Agile, I have also heard that they have found certain features in Rally more useful. But I don't know, I haven't used Rally to that extent.

I would rate this solution 7 out of 10.

We use it for project and sprint planning and day-to-day bugs. We also use it for documentation, engineering, and enhancements tickets and for creating the feeds, which are like new features.

We are most probably using its most recent version.

It has been very helpful for feature enhancements, release planning, and sprint planning. We have been using it for creating bugs, enhancements, and all the tasks for a sprint. It helps us in looking at the quality aspects of the product along with the volume, burndown rate, and a lot of other things.

As an engineer, I like that it provides you blocks to put in comments, code, etc. It helps in giving better information. 

It is very configurable, and we can do whatever we want. Jira dashboards are also good, and we use them extensively. We also use the tracking mechanism extensively. 

Another thing that I like a lot about Jira is that in the dashboard, you can plug the modules that you want. You can enable certain sections. For example, you can show trend history, open Jira tickets, etc. Some of the managers have created a dashboard for each engineer. So, it allows you to do all sorts of things.

There should be a way to look for specific comments. When we have thousands of comments on a Jira ticket, there is no way to look at the comments of a specific type. In the comments, if there is a way to put a tag, it would be helpful. For example, when there are a lot of lengthy discussions happening on a particular ticket, there could be a conclusion tag or something like that to indicate a conclusion. It would help in sorting the comments based on a certain category, such as conclusion. I should be able to tag a comment with something like ##dev_conclusion##, and someone looking at the comments should be able to expand all the comments and search based on this tag. Some of our tickets can go up to 100 or 200 comments, and it currently takes a lot of effort for someone to go through them. It would be good if there was a way to preview the comments.

We want Jira to be the single tool that people use. We lose a lot of information when working at the ticket level in Jira. We don't want to have discussions in Confluence and design docs somewhere else. Currently, we make some decisions outside, and we make some decisions in Jira, and there is no combined way. There should be a way to integrate documentation into this, and I should be able to directly update the documents. They can also incorporate a review mechanism for documentation. I should be able to assign a sub-comment to someone to say, "I'll respond to it," or I should be able to tag someone to say, "Can you please look at it?" We should be able to use a workflow. There should be some built-in intelligence where when there is a design document in a Jira ticket, the signoff should be done by certain people. Currently, the documentation is completely separate. If there is a way to get the documentation into this whole workflow, it would be useful.

I have been using this solution for seven or eight years.

Its stability is really good. There is no doubt about it. Sometimes, we have performance issues. That's mainly because a lot of people have standup meetings between 8 am to 9 am, and everybody is using Jira at that time. The number of connections is at a peak in the morning hours. If I was a Jira development engineer, I would be thinking about a mechanism to ease that. Other than that, it is pretty stable and reliable.

We didn't have any issues with scalability. We create hundreds of tickets every day. We have between 1,000 to 2,000 users across all departments. It is being used extensively, and its usage might increase.

I didn't have any contact with their technical support. We have a Jira maintenance team. We have a Slack channel, and if there is an issue, we send it there, and the team looks at it.

I'm not a part of the team that takes care of its deployment. We are a big organization, and I am an end-user of it.

I would advise having proper planning because you don't want to clutter your Jira. Without proper planning, you would go on creating a lot of labels and other things, which would be of no use. You need to do release planning and then accommodate things into Jira. 

A lot of companies have a separate release planning team, and then there is a separate Jira infrastructure team. All these teams should think and work together. Otherwise, everybody would be creating their own tags, which won't make sense. I might create a tag for daily bugs, and someone might create another tag for the same thing, which would result in cluttering.

I would rate it an eight out of 10. Jira is an amazing tool. There is no doubt about it. We have no thoughts of using any other tool.

We use it for client ticketing. We have managed services agreements with clients, and we use it when they have issues. It consolidates well with their IT ticket system. We are the first pass on the ticket issues. If it seems that a ticket belongs to them, we can easily pass it onto their system and their people. So, it is a ticket system for our clients.

We are using its cloud version, and it is hosted in Atlassian's cloud system.

It is not problem resolution by email. It consolidates everything in one place. We have unique cases that don't fit a particular engineer, and we're able to assign those on an ad hoc basis. It is a good process. For example, if it is a network issue, it goes to engineer A, and if it is an Azure issue, it goes to engineer B. So, we are able to quickly route it to whoever needs to resolve the situation without overview intervention. I like that feature.

I like seeing which tickets are open and what our response rate is. They have a lot of good metrics in their system to see what's going on.

I interface it with Slack, and that's a positive. We get our notifications in Slack, so everybody doesn't have to be an agent in their world for us to see everything, which is a positive.

I would like our clients' IT group to be able to have oversight without setting up agents. We're managing tickets, and I'd like their IT group to see everything we're doing without having to set them up as agents. There should be a better way of managing their users. I've got such requests, but Jira is expensive, and it is difficult to pay an agent fee for somebody else to view these tickets. Currently, the only way in which I can do that is by setting a user up as an agent, and it becomes cost-prohibitive. They need to do a better job on ticket viewers.

If they had a customizable dashboard, it would be great. There should be one with a public URL so that I could share it amongst other viewers. This is the beauty of Smartsheets. With Smartsheets, I'm able to have a customized dashboard. I can bring everything into Gantt charts for budgeting, performance, etc. There is one point of accessibility for our clients so that they can see the program in a snapshot and get whatever assets they need. I love that about Smartsheets, and I wish Confluence had something similar.

I have been using this solution for about two years.

Its reliability has never been a problem.

It works for us. We're probably managing about 25 to 30 tickets at a time. It is not like we're pushing the system.

Across the board, we might have about 100 users. Its usage is currently moderate. I would love to focus on one tool, but I use Smartsheets a lot for project planning. I know Confluence and Jira provide reasonable project management, but they're short in some features. So, unfortunately, I have to pretty much go with two tools. Confluence and Jira together make one tool, and Smartsheets is one tool.

I would rate them a five out of five. They are pretty good.

We did Freshservice for a bit. We got a client on Freshservice, and it was good for the time. We didn't really utilize Freshservice at the time. We had set it up for a client, and while setting it up, we customized it. We did a lot of front-end GUI tasks to make it work with their world.

A client pushed us toward Confluence and Jira, and that's how we started with them. I knew about Jira, but I never really used it internally. We had a client with whom we got a managed service agreement, and they said, "Hey, we're using Jira," and that's how we got in.

I did the setup, and it was easy. In terms of the setup, everything was intuitive with Jira. The setup is not intuitive with Confluence. It is not at all intuitive while setting up SSO.

It only took a few hours. It was really quick.

It was set up in-house. We didn't use a consultant.

I don't have the number, but I sure wish Jira was less expensive. Its price point should be a little lower, and it should be more flexible for users who are just ticket viewers.

I would rate it a seven out of 10.

We use it within our organization. 

It's to handle all the main technology projects. It's for managing mobile banking, internet banking, all the new products, and all technology-related projects.

We get the big picture of what is going on within a project.

The solution allows us to provide access also to the senior management, to see how things are progressing and to point out quickly what's going on, and help to focus energy on the things that are not going well.

The main benefit we got from the product is the consolidation. 

I like the roadmap or the new version with the roadmap that the solution offers. For us, the roadmap was a really great feature.

It's got very good portfolio management. 

The initial setup is easy.

The licensing is transparent. 

It's a stable solution.

Scaling the product wouldn't be difficult. 

Whether you are an expert in Agile or just it's the first time you are talking about it, it's a very user-friendly tool. It's a very simple tool. It's not complicated and even the integration and the usage is very simple. You don't need to be an expert. 

Whether you have small teams or big teams, it's the right tool.

We'd like to use it with non-Agile projects in the future, however, right now, it is a very Agile-focused product.

In general, however, as a solution, it's quite complete and I cannot speak to any missing features. 

I've been using the solution for one year now. 

At the moment, we have not had any issues with stability. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

At this time, we are not tackling scaling at the moment. The organization is not mature enough to scale up.

That said, based on the experience we have had now, if we want to scale up, it should not be that difficult.

We have approximately 200 people on the solution currently. Those users are mainly comprised of the software development teams plus some portfolio managers and program managers and the project managers as well.

We do plan to increase usage in the future. 

I have not had any interaction with them as we haven't had any major issues. We have a contract with the integrator, however. While everything is going well for the moment, we would have access to assistance if we needed it.

I've used Clarity, however, it was used in another organization.

The initial setup was not complex at all. It was very straightforward, very simple.

The full deployment took about three months.

We have four people capable of handling any management tasks related to Jira. 

We had the setup services handled by a reseller of Jira.

It was a very good experience. It was very fast compared to what we expected from the contract. It was a nice surprise.

We have yet to see an ROI as it's been just one year, including the three months of implementation. Maybe in the next six months, we can have visibility on that. For the moment, it's still in progress. We cannot say anything about any ROI.

We pay a yearly licensing fee for an enterprise-level license. 

It's quite similar to the pricing that they have on their website. It's quite transparent from their site. They have a package that charges per user, however, they have some scalable packages, for zero to 10 users, from 10 to 20, from 20 to 50, and so on. You can choose, depending on the size of your company or the number of users. The costs are quite transparent.

While everything is included in that package, the integration or the customization is a different fee. There's a project apart from the integrator, which may vary in cost.

We are just customers and end-users.

I'd rate the solution at a nine out of ten. There's always room for improvement, however, it's a very good solution.

I would recommend the solution to others.