Jira Reviews

I have been the product manager for several years. I use it day in and day out to manage my team. I manage two teams at the moment and they are pretty large teams. Each has a minimum of about 12 people. We use not just agile, we use a scale model framework. All the work is managed through two pieces of software we use. One is called Jira Align. For the portfolio level software, what Jira bought recently, the previous name for the software was AgileCraft. All of the portfolios and features come loaded in Jira Align. From there, they will be composed into stories in Jira. That process is done using programming preventative planning. We do it every three months.

All of the stories are tracked. We have a workflow defined and we have statuses defined. As the team works on the story, the story moves from one status to another and we close them when everything gets carried over to the production release.

The workflow is the most valuable aspect of the solution for us.

The user story map is excellent. The features can be composed into stories and they can be allocated to each of the sprints in a program increment. It allows you to see all that in the user story map, and you have various dashboards to see the stories in various views. You can see them as a backlog view, for example, or you can see as an actual sprint view.

There are excellent reports that come out of the data for every sprint so that you can do metrics on each. You can measure how the team is performing with respect to burn down charts, or with respect to how many story points were produced, or how many stories were moved out. For this, you can gauge the performance of the teams very effectively.

The solution needs performance improvements. We see that a lot of times it's clocking whenever there's any abuse.

When we switch from one view to the other, it takes some time before that view is presented. The performance for different dashboards, whenever they are loaded, it takes more time than you're comfortable with. Whenever you move from one dashboard view to another dashboard view, then it should come up quickly. Right now it takes a long time and sometimes it clocks. The overall product performance, whenever you switch a view is what they need to work on.

Whenever you edit a story, whatever you have changed takes a bit of time to save.

The integration between Jira and Jira Align needs to be better. There's a lot of differences between the two systems. I believe what happened was Jira bought this software from a different company called AgileCraft. And that integration is still in process, and, because of that, there's a lot of differences between the statuses. That sometimes creates a lot of confusion for senior management whenever they're reviewing performance across teams. Better integration between Jira and Jira Align is on the top of my "most desired upgrades" list.

The solution should improve performance when there are multiple users.

I've been using the solution for about seven years now.

Whenever you load different views, it takes time. That's the only major issue. I didn't see any major glitches due to the fact that Atlassian is really good at catching them. The stability of this product is really great. I've been using it for, as I said for six, seven years now. I'm never unhappy with it.

Our entire company, whenever there's a new division that goes into the agile mode of developing software, brings on Jira.

It's really scalable, however, at the same time, you need to really throw hardware at it to offer better response times when you add users. That goes without saying for most of the software.

We currently have 2,000 users on the solution. We plan to continue to increase usage in the future.

We have an internal tech support team for Jira. We contact them whenever we run into issues. We have a platform for IT tickets. We use that to call them. I haven't directly called Jira Atlassian at any point, so I can't speak about their direct technical support.

I have used other packages for agile project management.

I wasn't involved in the initial setup, however, we have a Jira administrator and they have a group, and that handles it. I implemented Jira for my teams. I added users to roles on the system. Roles such as developer, administrator, approval, managers, etc. That is all done by myself. In terms of that task, and setting up a project, it's fairly easy.

Implementation is a multi-year process. Right now, the whole company is on Jira. Whenever there's a new group, it gets added, and a new team is created. It's always a work in progress and it's not very time-consuming.

I would say the training of people on how to use Jira effectively takes some time. It's very intuitive, however, at the same time, a little training goes a long way in utilizing the software in a much better manner.

We are using the latest version of the solution.

It's a great piece of software. If you really want to do agile software project management Jira is definitely should be a top choice for you.

I'd rate the solution eight out of ten.

We use it for requirements gathering. We raise our tickets; it takes tickets in the engine. We also use it for bug tracking and integrate it with the X-ray for testing.

Jira is a one-stop solution for all the requirements of an Agile project, including SSL. It's easy to use, and it also offers excellent notifications.

Jira has integrations with almost all other build management and alerting tools, both open-source and licensed ones. There are limitations to its data.

It lacks features to cover all testing aspects, so we often integrate it with other plugins or tools like X-ray. It would be beneficial if Jira included modules covering testing elements such as test planning, mapping test cases to requirements for traceability, tracking execution status, and managing different branches before release. Since Jira lacks robust support in these areas, we rely on additional tools like X-ray, which can be integrated with Jira. If Jira could incorporate these features internally, our processes would be streamlined.

I have been using Jira for 5 years. We are using the latest version of the solution.

I rate the solution's stability an eight out of ten.

Around 100 users are using this solution. It is scalable too.

I rate the solution's scalability an eight out of ten.

Customer support is good.

Positive

Jira is not difficult to install. We have an IT help desk team to take care of admin configurations, installations, etc. Everything is managed by different teams.

There are roughly around 50 people for deployments or maintenance overall.

The product is moderate and has a yearly subscription.

I rate the product's pricing a five or six out of ten.

I have used some other test management tools, such as ALM. If it is a full model, it'll be too difficult to manage in Jira, but for Azure projects, Jira is the best. It depends also on the needs of the project.

My advice would be to consider having a Jira license. There's a level of customization available, along with flexibility in pricing plans, so you can tailor your request according to your needs. This allows us to access features that align directly with our requirements.

Jira has integration capabilities with almost all build management and alerting tools. It offers seamless integration with both open-source solutions and licensed ones.

Overall, I rate the solution a ten 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.

Similar to the whole solution stack, we use Jira for security and for operational data storage. We also use it for custom-made API structures, moving data from the cloud to legacy on-prem infrastructures so we can use it to develop failing interfaces. We're customers of Jira and we license the solution. Our company has a form of strategic alliance where we buy the product, pay the fees and use the solution. I'm a senior technical project manager.

The benefit of Jira to our company is that the product is extensible. We can integrate other tools and different interfaces into it. You can look at what's being done, how it's being done and know how to improve it. That includes things like optimizing performance or scanning the structures we build for security vulnerabilities. Extensibility is the most effective way we can create products and services for our clients.

The value of this product is that it offers a common language set so we can bring people into projects and get them up and running almost immediately. We know the language. It's the training and education content that's key and there's enough out there, whether it's paid training or free training, that gets people up to speed pretty quickly. Following on from that is optimizing the training for a given initiative or project. 

Although this is a somewhat old-school approach, we'd like to see some common building block approaches to certain things. We do a lot of coding and swapping things because there's a lot of common non-functional capabilities we have to share based on our own company policies. In that sense, it would be helpful to have some sort of modular building blocks that are in some of these up-and-coming extensible capabilities, like how you interface the next level of security scanning code or cloud to cloud capabilities, anything like that would be an improvement. These are expensive things to build and give out for free. At least knowing what's in the headlights for the products together with some good specific industry demos would help, whether related to the financial sector, healthcare sector, whatever. There isn't a lot of that; as things stand, they're generally offering demos with people talking about how you could have a secure way of developing a code for a HIPAA mixed standards or whatever. More documentation on how to precisely use the solution, particularly in a given industry sector, would be helpful.

We use a lot of third-party monitoring and although the extensibility is there, a monitoring tool suite as you get in production would be helpful. 

I've been using this solution for 10 years. 

This is a good product, it's served us well. I don't really have a lot of issues with it so I rate the solution eight out of 10. 

We used it in my previous organization for project management, product management, and release management. In my current organization, where I started working a week ago, we are using Jira strictly for help-desk tickets. We are using DevOps for our release management. So, we've got DevOps, Jira, and some homegrown stuff, and I'm trying to figure out what's going to work best for this new organization.

I've used Jira and Confluence previously, and this is my first time using the help-desk ticketing system. It is cool and not a whole lot different than SolarWinds or Zendesk, except the appearance of it is more Jira.

We were using Microsoft OneNote for systems engineering and network engineering. It was being used for our documentation, environments, and services, and it was a nightmare. We transitioned everybody and copied everything into Confluence. We were then able to tag specific tickets to the notes, and there were links between what work was recently done and the most updated notes in Confluence.

The roadmap feature and the ability to integrate with Power BI are probably the most valuable features in it. It is a great solution. I absolutely love it. It is a tool that was designed for project management, and it has been awesome to work with it so far. I also love Confluence.

They can maybe dumb down the directions for building the automation a little bit because to be able to build out the automation, I had to play around with it and learn what all the fields meant and what they were referencing. I don't have an IT background originally. My background is in biology, and I got into project management by chance. I am good at it, but I haven't really worked with coding languages. In terms of writing automation, it is easier for devs because they intuitively know what they're being asked, but as a PM who originally didn't have IT experience, it was a little bit daunting at first.

It could also have an extra hierarchy to be able to allow tasks under stories. It could be the way it is set up at our organization, but currently, under stories, you can have sub-tasks, but you can't create a task. Being able to customize your hierarchy a little bit more would be beneficial because sometimes, the devs would say, "Well, here's a story, and now we need sub-tasks," but as we were building out the sub-tasks, sometimes we had to go a step lower to dig in a little bit more, and we couldn't do that.

I have been using this solution for two years.

It has never gone down for me. It was always reliable, even from the mobile app.

It was fine. It seemed to integrate with all of our systems with ease. At my previous organization, there were probably 500 or 600 people using Jira. There were many different roles including product management, project management, VPs of IT and Ops, IT data services, developers, network engineers, systems engineers, and CBAs. It was a full scale of IT professionals.

At my current organization, where I started working a week ago, we are using Jira, but there are only a handful of people who are actually using it. It is strictly for help-desk tickets. I am trying to implement it and roll it out to the organization on a much larger scale, and I'm going to have to talk to them about pricing and other things. In this new organization, there are probably about 500 or 600 employees in total. Assuming I get the buy-in from everyone, which I don't think would be a problem, I would probably need at least a hundred licenses for users and then expand from there as needed.

I haven't interacted with their technical support, but I bet they would have been awesome.

I have used Smartsheet, MS Project, and Trello. Jira is more software-development-specific and a much easier tool to use.

In my previous organization, I believe its initial setup was complex. I was not at the administrative user level. I was given admin privileges for certain projects but not for the whole Jira. This is the first time I actually have admin privileges over all of Jira, and it was set up for me.

It probably took a few days. It would have also involved a lot of conversations and other stuff.

It would have been in-house. In terms of maintenance, it didn't seem to need maintenance from our side.

I would advise going with the entire Atlassian suite. Don't just use one aspect of Jira, unless you have a very specific need for using bits and pieces. Jira is better when Confluence and everything can be integrated, and you have source code management and all of that from the same software or platform.

I would rate Jira a ten out of ten. I love Jira. It has the ability to just do everything, and it is a one-stop shop for all of your IT software development needs.

I use the solution in my company as an ITSM tool. Our company's service desk and those working with the engineering team use the tool.

The integration between Confluence and Jira, along with Jira's ticketing system, is a valuable feature the product offers its users.

I opted for Jira since it was offering ITIL V4, and there seems to be a compatibility between ITIL V3 and ITIL V4.

From an improvement perspective, it would be better if Jira could offer more in the area of data analytics similar to what Power BI and Qlik offer to users. The tool currently lacks in the area of data analytics.

Jira needs to consider lowering its prices considering the competition in the market.

I have noticed a problem with Jira in the Philippines. In the Philippines, there are only a few companies that offer local support, which is alarming. In my previous company, when we requested support, basic support was not provided, and we had to schedule and deal with everything on our own.

I have been using Jira for around two years. I am a user of the solution.

It is a stable solution.

It is a pretty much scalable solution.

The solution's technical support is good. I rate the support a nine out of ten.

Positive

I have experience with ManageEngine and ServiceNow. If I need to deal with a project involving retail business, then Jira would be a poor choice because dealing with a retail business requires a tool to have an approach different from what Jira offers. Compared to ServiceNow, Jira is a bit better.

The product's initial setup phase was straightforward.

The solution is deployed on the cloud.

The solution can be configured within a week or so. If there are changes to be made in the solution, then it requires more time to configure it.

If I compare Jira's licensing model with that of other products, I think that the other products have a much better licensing model. Considering what is happening in the market presently, and as people are moving away from Jira and ServiceNow, more and more people have started embracing cheaper products in the market. I rate the product's price a four on a scale of one to ten, where one is cheap, and ten is expensive.

It is important to know that my company uses the free version of the solution since we are not a big organization. My company is currently looking into the configurations and other areas before going for the paid version of the solution.

Performance-wise, Jira is a good solution, but the problem lies in the part of its licensing area.

I rate the product's price an eight out of ten.

We use Jira mostly for task coordination and assignment. Additionally, scrum methodologies defined work items and bug issues. If we create any bugs all of them are fixed.

Jira can improve by making methodologies better, such as scrum and agile. Additionally, improvements in Kanban boards are needed.

I have been using Jira for approximately five years.

The stability of Jira is good.

Jira is scalable, this is in part because in our company we use it on the cloud.

We have not needed to use the support from Jira. It is easy to find information on Google or any other search platform. If we encounter an issue we can find the solution online.

The initial setup of Jira was simple.

The standard package of Jira is for 100 users. They should offer more packages for other increments, such as 500 or 2,000. In my previous company, there was a free package that provided a minimal number of users.

I rate Jira an eight out of ten.

I primarily use the solution for project management. 

The product is quite easy to use and simple to navigate.

The solution isn't too difficult to learn.

It's flexible and it can provide a lot of different options, such as dashboards, that you can create and manage. You can really tailor-make your own dashboard depending on your needs.  

It's quick and very stable. 

I don't see many issues while I'm using it.

You can basically communicate with all kinds of different teams that are using Jira and you can do that under the product, as a single platform.

Sometimes the solution doesn't communicate well with other platforms. It's quite difficult to integrate things and make the data flow from A to B, to Jira, and then back to other areas.

Nowadays, you see a lot of product management tools, like monday.com and they are very user-friendly. They offer features that allow for cosmetic changes, and you can actually change the color and the form to your own liking. ira is lacking some of that flexibility. It's not critical, however, for the wider user base, many would like to see that.

I've been using the solution for three years. It's been a while. 

Overall, the performance of the tool is quite reliable with few bugs or glitches, and it runs very fast in the browser It doesn't crash or freeze.

The solution can handle a lot of tickets. I've seen it handle more than 10,000 with no problem. It's almost unlimited in terms of scalability.

I'm a customer and an end-user.

I'm using the latest version of the solution right now. I cannot speak to the exact version number we are on currently.

I'd rate the solution at a nine out of ten. We've been very happy with its capabilities. 

I would recommend the solution, as it is quite powerful.