Jira Reviews

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 Jira app, not the desktop version. 

I work at a university and we use Jira to create tickets, epics, and stories. We link Jira to spec documentation with Confluence. We can also link it to TestRail.

Within the university that I work for, there are roughly 4,000 people using this solution — all staff members use it. 

I like that it's integrated with the specs. You don't have to put the specs in a shared folder or a shared server. It's all linked together with Confluence. We just put the specs into Confluence and then link it to the ticket in Jira. Once our developer has finished his development, we can link it to TestRail to create test scenarios, test them, and analyze the results of the test.

It should be connected to ServiceNow. We use ServiceNow for deployments from our test environment to QA, then to production. If it was linked to ServiceNow, it would be perfect — it would be more integrated. Still, at least we can link our test scenarios, specs, and the tickets themselves so we can track the requirements — that's good. We have to use ServiceNow separately to deploy and move corrections from one environment to another.

There are a lot of features that need to be added on top of Jira for management, sprint planning, and agile topology for project management. My project manager says that there are not a lot of features for project management in the agile mode. They have to buy other products to put on top of Jira to be able to properly manage and to track what people are doing.

I have been using Jira for two years. 

I was always able to connect. Once you're inside, it's good. We have never experienced any bugs, glitches, or crashes. 

I think it's scalable. It can be integrated with other products easily. It's not a standalone product. Integration is the most important thing when it comes to scalability. I believe it uses a certain technology to make it even more scalable. 

I've never had to contact support. I've never had a bug or a bug message that I needed to open a ticket for. 

We used to use Remedy, but it didn't have everything that Jira has. Jira supports agile methodology. I used Remedy with waterfall projects, but for agile, Jira is the way to go. I've heard people say that Jira is better than DevOps tools.

I don't think it's complex to set up. The features are standard and come included with the product. You only need to know how to use it, create new Jiras, and how to link them. I don't think the setup is complicated. I've installed Oracle E-Business Suite a lot — that's complicated. Jira is much more direct. 

If you're interested in using Jira, you have to just go ahead and buy it and use it. Try to use all the functions that are available. There's a lot of things to do in Jira. I recommend it. 

Overall, on a scale from one to ten, I would give Jira a rating of seven.

My people use ASS. I can define spins, I can define roadmaps, I can define components, I can do releases, I can define all kinds of issue types, heartbeats, some of those things. I'm using it for both business and software. In software we have Scrum and Kanban onboard, whereas for business we have the service and then there are those other options. We have multiple use cases. I'm the director of the company. 

I like almost everything about Jira. It defines how we track time and the way we define permissions. We can create multiple boards for the same product backlogs. 

I think that for users the solution is very intuitive but for project administrators, the way the product is defined is not very intuitive. There are too many ways to do the same thing. The setup of Jira sometimes becomes very, very cumbersome and difficult. It's not very easy for people on the project admins to really understand how to set up the product because of these features. If they were better organized and the documentation improved so that people would actually be able to figure out how to use Jira, that would be helpful. There are not many videos and it can be very challenging for anybody not familiar with the product. There are 50 users on the project I'm working on. 

I've been using this solution on and off for the last eight years. 

The solution is stable.

The solution is scalable.

We haven't really used technical support. 

The initial setup takes a bit of time because it has so many features that you should be aware of, but of course it provides a lot of out of the box features that you can use right away. You can set up in 10 minutes or 10 days, it's very rich. I was able to do the deployment myself with some extra help. 

For up to 10 users, the solution is free but above that there are licensing costs.

I would rate this solution an eight out of 10.

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 the solution primarily for project management. We organize our work by projects with epics, et cetera. Below that, I believe we are using a Zephyr plugin for QA. We don't use it for product planning.

I would say it's a necessary evil to use a product such as Jira. All of these solutions are a necessary evil. They all have their pros and cons.

For what the solution does, it's fine.

The solution offers a lot of plugins.

The solution is very configurable.

There's a bit of a learning curve, which I'm not a huge fan of. It's not exactly user-friendly per se.

I would prefer it if the solution was more intuitive.

There are just so many options, that it's pretty overwhelming as a product. There's too much to focus on.

We do find that we need plugins and have created integrations with more robust analytic solutions than Jira provides.

Personally, I'd like it if there was more flexibility in how you could manage the backlog at a project level.

I've been using Jira for about six months. It hasn't even been a year yet. The solution is still very new to me and I am still learning.

The solution is very, very stable. There's no problem in that sense. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

You can easily scale this solution. If you need to grow it out to meet your company's needs, you can do so. That's not a problem.

We have about 300 users on the solution right now. They include developers, administrators, senior leadership, analysts, designers, and project managers.

I haven't used technical support at all. I can't speak to their reliability or level of knowledge.

Although I wasn't hired at the outset of the company, it's my understanding that they've always used Jira as a solution.

I wasn't involved in the initial implementation of the solution. I just started working with the company six months ago. Honestly, I'm still learning the solution.

I don't have an opinion on the pricing or licensing. It's not really a main concern of mine. I don't have access to any information about what the company pays.

We're just customers. My company doesn't have a professional relationship with Jira.

I'm not sure which version of the solution we're using. I'm not sure of the last time we updated the solution. I've only been at the company for six months.

I'd advise other companies to dedicate two full-time people to learn the solution and train other team members. It's a big learning curve for users. It takes time to get into it. Having dedicated trainers would help onboard people.

Overall, I'd rate the solution seven out of ten. If it was more intuitive, and there was less of a learning curve for new users, I'd rate it much higher.

I am generally managing development teams in a position of delivery lead. I have also been involved in several positions where I acted as a Jira administrator, setting up delivery processes and production support.

I appreciate the openness of Jira. It is based on a concept that is well understandable and works in a logical way, allowing customization of any process that needs to be applied. Jira dashboards and support for JQL queries allow navigation through any data that customers have put in. It has open standards for integrating Jira into other tools.

The only issue I see is the licensing model of Atlassian for Jira. Many customers face issues with this model, often resulting in solving the issues in a nonstandard way, which may double the cost of the product. This can block many customers from utilizing Jira Service Desk, as it doubles the cost compared to the regular software management Jira.

I have been working with Jira for twelve years.

It is not a problem at all. The solution is very stable.

Jira has a good community around the software. They have a good forum where you can find most of the issues that others have already experienced. However, there are specific cases where you need to contact Atlassian support directly, and the responses are not that great.

Positive

The price is average, and it's definitely worth being paid because it is an industry standard in software delivery these days. However, there are specific use cases where the price isn't acceptable for clients.

I rate the overall solution ten. I am hesitant to use anything else for project management. There is some AI integration available on the cloud instance of Jira, which helps compiling JQL queries, particularly useful for business people who do not know the syntax.

I am the software developer manager and I use Jira to manage team performance. We're also starting to use Jira for our drives. I used Jira before, for creating user stories from boards, to discuss issues, and many other tasks. Today we use Jira, Confluence, and BitBucket in our work. We practice scrum in our organization.

It improved with many exiting features to manage user stories, planning and retrospective meetings very productive.

The documentation is very good.

The solution is stable.

You can scale the solution easily.

It's comparable to Azure DevOps.

It's a very complete product overall.

It would be ideal if Jira had future functionalities to integrate more easily with various aspects of code reviews.

It would be nice if, in the future, Jira worked a bit more like Azure DevOps in order to be able to manage work in progress and have the task measurements in strategies for the stories.

In the future, I would like to have traceability features. For example, when you create a task or a sub-task that's related to code. In this task, if we could create a method for retrieve customer information, that would be helpful. In that case, I would want to train with the source code later.

I'm new to the company. Although I've worked with Jira before, I've only been at this company for one week.

Atlassian solutions for me are very good solutions. They are very interesting and very productive. As a user, it is necessary to have a unique portal to make traceability between sub-tasks related to code or programming. You can create and screen or implement a function or a class, related for example to the code that you are pushing in the repository or commit in the repository. If I open the sub-task, I will see the code related to the sub-task. It's very similar like Azure DevOps. Azure DevOps, however, has this functionality for traceability. This functionality will be amazing that Jira would implement something similar.

I prefer to use Azure DevOps instead of Jira for stability or the frequency of use. In my case, for example, I feel that more users, more companies don't think Azure DevOps makes a good choice due to the fact that the cost is higher than Jira.

The scalability is very good if you're carrying a lot of projects here, and if the company needs to have a lot of people to PEA development centers in Mexico. Our technicians can easily test the tool and scale it in order to develop projects.

We do plan to increase usage. We're already training more users. We're increasing quickly so that our teams will be ready for upcoming projects.

We have manuals, technical support, and also technical specialists in the company. I haven't had the opportunity to use directly call the technical support from Atlassian, however, the technical documentation that I have reviewed is excellent. We're satisfied with the level of service we have access to.

We also use Azure DevOps. They are both very similar. The main difference is Azure offers traceability.

The solution is easy to implement. We have the cloud version of Jira in the company, and we don't worry about maintenance, it's automatic.

The cost of Jira is okay. It's better than Azure DevOps. We don't have any licensing fees that I know of.

While I'm new to the company, it's my understanding that it is a partner of Atlassian.

We use the latest version of the solution, as we use the cloud, which updates automatically.

Our company has both Azure DevOps and Jira. I use Jira, and Azure DevOps is used for other purposes. Most projects, all projects that are using Azure DevOps are legacy projects. The new projects and new solutions are using Jira.

On a scale from one to ten, I'd rate Jira at a ten. It's a very good product.

Both tools, Azure DevOps and Jira are at the same level. In terms of preference, I typically choose Azure DevOps for familiarity but not for features. For features, both are the same. For example, Jira has amazing features that Azure DevOps doesn't have, and also Azure DevOps has the flexibility that I like very much. Both tools have different interesting aspects. However, if Atlassian would implement traceability, I would prefer to use Atlassian. For me, it's more complete and allows for smaller teams than Azure DevOps.

Jira is a project management tracking tool, and it would be great to see integration with the source front or Azure DevOps, etc. The history of tasks, such as check-in and checkout, is not maintained under the particular Jira ticket. For example, in Azure DevOps management for a work item you can find out any chain set and dependency.

I've been using Jira for more than two years.

It is a stable solution.

We have around 2000 plus users, so scale wise, there are no issues. We can easily scale up with multiple users.

I'm coming from an Azure DevOps background, and we use the integration board. It is very easy because the source code is there under one umbrella; however, Jira is not under the Azure DevOps umbrella. If your company is using Azure DevOps or Git as a repository, I recommend using the Azure DevOps board rather than Jira.

I would rate Jira at seven on a scale from one to ten.

We use Jira to manage what is happening in our projects, such as application development lifecycles.

The most valuable features of Jira are the dashboards and user interface. The processes within Jira to monitor, maintain and release are beneficial. It is a continuous development solution.

I have used Jira within the past 12 months.

Jira is a reliable solution.

I have found Jira to be scalable.

The price of Jira could be lower.

I rate Jira an eight out of ten.

We use Jira for ETCM. It's for ticketing with QRadar.

We integrate Jira with QRadar which is helpful.

The performance is quite good.

It has real-time collaboration. 

It provides good visual data easily.

While Jira integrates well with QRadar, it is not integrated with Splunk for example.

I would like to see more integration available with more tools.

Jira is not used in my company; in fact, it is not used at all. Jira is a project management tool that I use at school and during my internship.

Jira is stable. I have not experienced any issues with the stability of Jira.

We have not had any issues with the scalability of Jira.

They provide technical assistance. Whenever you need something technical, they are quick to respond.

The price seems reasonable to me. It's very similar to Splunk. 

I don't believe it is expensive. 

I'm not sure if they provide a free version, but we need free versions of everything to try before we buy. 

I believe we simply require a longer, free version.

The initial setup is simple. I didn't do it myself, but I've read the support, the guide, and it appears to be simple.

I did some research for a school project. I needed to compare it to Splunk and a few other tools. As a result, I'm not particularly interested in purchasing them.

I don't use Jira very often, and I don't have a lot of experience with it.

I would rate Jira a seven out of ten.