Jira Reviews

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.

I use it to manage my scrum projects and some of the Kanban projects.

In terms of version, they have been updating it every three weeks. It is a kind of a sprint that they do, just like Google Chrome. So, there is no going back and forth. We use a cloud-based application. So, it is always the updated one.

The type of cloud depends on the client. I've been through all kinds of situations: completely public, semi-public, and private. If it is a public cloud, then it is directly from Atlassian. They are providing it. So, there is no middleware.

It definitely streamlined the process of managing the projects. Earlier, we had a system scattered all over the place. We had information in Excel, Microsoft Project, and some of the other applications that we have, but now, we have everything in Jira itself. So, we create user stories and groom the product backlog. We have kept everything in Jira. It is our single source for project information that anyone can go to. So, we could see a lot of transparency with Jira.

Overall, it is very intuitive. It is so lightweight and easy to use. It is easy to manage our product backlog and user stories, and it produces great reports.

It is good for single projects, but if you have to manage the portfolio level of the projects, they have a few add-ons that we need to buy and integrate. They can improve this part to manage it in a better way.

It is not capturing the number of hours for which each person has worked on certain things. We use many add-ons to let resources enter the time in the user story itself. We use an add-on called Tempo, but it is kind of a lousy add-on. It is not straightforward. Rather than helping us, it creates a lot of confusion. So, instead of looking out for the additional add-on, I would prefer to have the timesheet entered as a part of Jira itself. They are anyways capturing every information they could for each user story, and then we are able to break down all the task lists. For each task, we're also assigning a resource. So, while we're doing it, why can't they allow the users to enter the time that can be created as a report? Right now, we need to acquire the add-on, and the add-on is not great. It is not helping. The add-on is also not free.

There could also be some additional reports.

I have been using Jira for seven to eight years.

Stability-wise, it is very good. It is very lightweight. I have used other enterprise-level products to manage the same kind of scrum and Kanban projects and other projects. Other products have many enterprise-level features, but they're very slow and kind of hard to manage.

It is a cloud-based one, so I don't see much difficulty in scaling it. If you want to go from 100 users to 200 users, you will be able to do it without much hassle.

I've been doing a lot of consulting. So, I've seen from five users to the entire organization with more than 500 people using it.

I did contact them through email and discussion forums. I had a limited opportunity to work with them. So, I don't know much about their support.

Jira is a kind of the last one I settled on. Before that, I have used products such as Rally and VersionOne. These two are enterprise-level scrum and Kanban tools that are similar to Jira. 

I have also used Asana and Trello. Trello is lightweight, but I wouldn't call it equivalent to Jira. Jira has many features that not many solutions have. 

Most of the time, we are working with the cloud-based one. So, we don't have to set up everything. It is all there. You just buy a monthly subscription package. The workflow configuration, however, would be a bit difficult while you're trying to set it up. In addition, if you have to go down to the permission level, it is a bit different.

Workflow-wise, you need to plan well because once you configure it, you cannot often change a workflow. For each project, the workflow might be different. You might have a development team, a QA team, a configuration team, and a deployment team. When you start a task, you just need to make sure you are covering everyone. In terms of the workflow, you should know what would happen if someone is not there, and what are you going to do. So, you need to make sure that you are covering those things. Other than that, you need to know how much you are going to take care of the hierarchical level permissions. These are two primary things, and then, later on, you can relabel quite a lot of things in terms of how you're using the backlog product and user stories.

I would rate Jira an eight out of 10.

The primary use case of this solution is to manage work, to distribute work to the teams, and we use confluence as a SharePoint for documents and to use AgileCraft.

This solution is easy to work with. It's easy to understand, and easy to navigate. 

it would be helpful to have a better tutorial for learning and to have a better understanding of what the features are and what they do.

In the next release, I would like to see better integration with other software. Many companies have a lot of peripheral systems. They have ServiceNow or they could have something else. How do they integrate your stories, your sprints, or if you have confluence, or SharePoint when you start using Jira? 

The challenge is when you have someone who is not using confluence, but they have SharePoint or ServiceNow.

How do we connect, or integrate our stories with Jira, so we don't have to have the information in three different places? 

The integration and integration threads would help Jira going forward.

I have been using Jira for more than one year.

This solution is stable. I haven't experienced any issues, it works fine.

We have approximately 100 users. It is not used concurrently. There could be anywhere from 20 to 30 users in a day.

We have yet to explore the scalability, but we hope that it is easily scalable. For us, that was the purpose of using this solution in our organization. We plan to use SAFe, a scalable scaler, scale agile.

I have not contacted technical support,

The initial setup was done by two local employees.

This an area that I would like to explore more from an admin perspective, on how to set up teams, what are all of the things we can do, and to set up the right way so that we can get the most potential out of the software.

I am not involved in the pricing. We have a sales team to procure our licenses.

I don't feel that price is an issue.

I have heard of many other solutions, such as Rally, but I have not explored it or compared it with Jira.

It's difficult for me to tell you everything that Jira has to offer when I am still learning. I am trying to educate myself to have a better understanding. I want to learn more.

I would rate this solution an eight out of ten.

We follow an Agile framework and use Jira for sprint planning and management.

The scrum dashboard is the product's most important feature. It provides an overview of tasks, who is working on what, and the status of each task.

It offers very good APIs for creating custom integrations and has many built-in integrations with other tools.

The solution heavily focuses on the Agile framework, which might only suit some business use cases. This particular area needs enhancement. 

I've been using Jira for about three years.

The platform is very stable. I haven't faced any stability issues with it.

Approximately 70 to 80 people are using Jira in our organization. It is a scalable product. 

Setting up Jira takes some time. You need to create dashboards, configure settings, and test those configurations. The default setup is straightforward, but understanding and applying the various configurations can be time-consuming.

For smaller organizations, it might be better to consider alternatives like Linear.io. But if you need an integrated system, especially with other Atlassian products, Jira is a solid choice.

It is widely used, so the transition is easier if someone moves from one organization to another that also uses it. Additionally, its automation features are powerful and can address many use cases.

The reports are useful, giving an overview of a sprint's progress and indicating areas for improvement. However, I have yet to use the analytics feature much.

I rate it a seven out of ten. 

We are using Jira for scrum, specifically for Agile Scrum. Most of the tasks are in Jira, including the dashboards and reports.

For now, we are using Jira for the scrum. We are quite happy with this as it allows for task management and report generation.

We can query the tickets and create dashboards based on these queries. This functionality is helpful for monitoring project status and tracking bugs. We are using Jira for scrum within the Agile framework. Tasks and dashboards are in Jira, which also assists in report generation.

I am unable to query based on the subtask and link by issue, which can be improved.

I have been using Jira for more than five years because my previous company also used it.

For stability, I would rate Jira as eight out of ten.

For scalability, I would rate Jira as seven out of ten.

I have not contacted Atlassian's technical support since another team handles these issues.

Positive

I have tried Trello, which is open-source and free, however, Jira is much more powerful.

The setup of the project in Jira is handled by our scrum master, who is not a very technical person, yet manages it efficiently.

For small companies, Jira is not affordable, leading them to use Trello or other free software. Jira is quite acceptable for medium to enterprise-level companies due to the features it offers compared to its pricing.

I have not used Asana, but I have used Trello. I find Jira to be much more powerful.

Overall, I rate Jira eight out of ten. I am quite content with its features and capabilities.

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.

It's pretty much for engineering development, Scaled Agile purposes for engineering development, for managing basically the epics and the stories and the capabilities and everything that we have to deliver in sprints. We're not using it as a ticketing tool or anything like that, for operations. We're using it purely for managing the development stuff in a Scaled Agile manner.

The solution is easy to use. It's pretty dynamic. It allows us to basically handle everything that we need in terms of a backlog, and we're trying to do it in an organized manner, so we know who works on what and how to size the story points so we can ensure that our epics burn down from sprint to sprint.

In terms of the general way that the tool functions, it seems like it's a pretty good fit-for-purpose for what we're trying to do. We've never thought about replacing it with another technology. 

The initial setup is pretty straightforward. 

The stability is pretty good.

There are a few things about it that I think need to be improved in terms of the ability to build reports. We would like to be able to use the data from Jira to help drive Gantt chart roadmap-type views of not only what we're building, but rather where we're going.

What we've elected to do in a couple of cases is just pull the data out of Jira and then pull it into Power BI so that we can try to get some of the more sophisticated information that we want out of it. We actually experimented with building portfolio views so we can see stuff in real-time. In some ways, it's okay. In some ways, it's just a little lethargic for our purposes.

We'd like to be able to manage things in real-time and by looking at stuff. We're doing PI planning, Program Increment planning, and that kind of stuff, and it's not always a good facilitator for that. We tend to pull it out and put it into other tools to manage that, and then we get it back into Jira as that's our system of record for where all the stories are kept. That's probably the biggest headache with it.

For some of the portfolio stuff that we did, the queries were so complicated that it was just taking forever. It was like watching paint dry for the results to come back. We would be in a meeting and then we'd hit a refresh and you're waiting for what seems like an eternity.

The solution could use API integration to take feeds from other tools so that we can read them better. We got one camp using an ITBM tool from ServiceNow. We have Jira running in this other area, and having an API between the two so we could actually collaborate between the two tools. However, API integrations with other tools would be helpful so we could either take data out of it or put data in it, thereby making it more of a data-driven platform that integrates nicer with other platforms. That, I think, would be something I would like to see.

I've been using the solution for four years or so. 

I haven't heard people really complain that it's unstable. We haven't had very many performance issues with it. I don't know if it was a network problem or what it might have been, however, I haven't really heard people talk about performance problems other than when we were trying to use it for portfolio views and that got kind of weird as queries were just complicated. Beyond that, the stability has been fine.

The issues that we have with scalability aren't necessarily with the tool as much as it's how we're using it. We're a big company so there are a lot of people using Jira, however, we don't really see how the projects correlate across different activities within the company. When we're trying to get two integrated roadmaps and trying to get to a point where we're collaborating, doing inter-sourcing of a solution, and we're all in Jira, there are times where we're in it and yet we can't collaborate and work together, and so we start replicating things across the two projects.

I don't know how much of that is the issue with using it how we are versus the product itself though. 

We have 8,000 to 10,000 people using the solution currently. That's across many departments. We are a company of around 150,000 people. There may be people using it that I am not even aware of. I only have visibility of what I'm doing and what I'm exposed to in terms of integration with offerings and that kind of stuff. I know when we were managing licenses, we used to have a DevCloud team. For their scope, it was in the 8,000 to 10,000 user range. 

The solution is being pretty extensively used. Likely usage will grow as the company grows and takes on new business. I don't know if it's going to organically grow exponentially as it's already being used where it needs to be used and currently we're only using it for development activities across the different offerings and platforms. It's not used as a day-to-day run-and-maintain ticketing system to manage customers or issues or anything like that. I'm sure there'll be some incremental growth as we take on new business and grow as an organization.

We use Jira. We use Confluence as an extension of that, and then we also use ServiceNow, the ITBM capabilities of ServiceNow as well.

We had a DevOps team that ran our cloud environment, and they basically spun up a project for us, and it was pretty straightforward. It's not like we were installing it in the cloud. People just said, "Here you go, and you can just start using it." After that, we just created a project for what we were doing, and then we were on our way. I wasn't really involved with any part that was problematic or anything.

In terms of maintenance, pretty much everybody is maintaining their own instance. We've got somebody that manages what's in the cloud for the company, however, it's pretty much hands-off in terms of day-to-day support issues. We had a few people that were supporting it when there were problems, however, it's just a handful from what I understand.

We're just customers and end-users.

We are likely using the latest version of the solution. I don't know what the latest version of Jira is, however, I'm pretty confident we are.

The advice I would give is it's not a solution for a novice person that doesn't know Scaled Agile. Users will get out of it what they put into it, and if you don't know what you're doing you could set yourself up for a nightmare when you're using the tool. My advice is that the better you structure yourself and understand Scaled Agile and how you want to set up the project the more successful you'll be at using it for your organization's purposes. If you're going in there as a novice that doesn't understand anything about Scaled Agile you could create a mess for yourself and then it won't give you the value you are seeking.

I'd rate the solution at a seven out of ten.

Jira is used for all the project management, on all the stages of project management. So then we create a Kanban board and move on to creating the stories.

We create the story points, break down the requirements, and then create the Sprint accordingly. Based on that, we can manage in Jira how many user stories we will pick in what Sprint. And based on the dependencies of the user stories, this is the flexibility that Jira provides. Then we have also got various, you know, sub-tasks, which we have to complete to accomplish the DoD (Definition of Done). We can mark the Sprint as complete when these particular tasks are completed. So that gives very good monitoring of the project where the project is

going on.

When it comes to the testing part, so testing is end-to-end on Jira. We can take the user stories based on the acceptance criteria. The test cases are created in Jira, and the business analyst team reviews those test cases. Based on their feedback, the test cases are updated. Those test cases are being executed. So there is clear tracking of the test execution, and all the test cases are also linked with the user storage. We have end-to-end tracking of what test case is executed for what user story. So that is the best part of Jira.

The monitoring, flexibility and tracking are really good in Jira.

When we use the plugin in Jira so, there are two different systems which we are working on, Jira and the X-ray plugin. The X-ray plugin should be incorporated into Jira because we have to fetch two reports. One report is faxed through Jira, and one can be faxed through X-ray. So there needs to be clarity about which the Jira team should reflect.

I have been using Jira for eight years. 

Jira is a stable product. I have seen the growth in the solution’s stability for the last eight years. The current version is quite stable and is a robust system.

Overall, the solution is scalable. Jira is quite easy to scale. If we have five projects working on Jira and we have about five more projects to be incorporated, it's easy to install Jira for those five projects as well. Presently, twenty five thousand users are using Jira. 

We have been using this for the last eight years and we are quite accustomed to that. We don’t need much support from Jira or Atlassian. Yes, but we have got an enterprise version of that, and their support is quite quick.

Positive

I was using HPE Quality Management Tool.

The initial setup of Jira is very easy. I have been an administrator, so I would say that because used to it. But in comparison to other systems, yeah, it’s quite easy and user-friendly. The deployment takes two to three days of time. Forty people are required for the maintenance of the solution.

I implemented it myself as an administrator of Jira.

Compared to the value Jira provides, it’s not that expensive. It has an yearly licensing cost.

Use all the reports which are generated. You have to make a system for the process. Here is a small example during a subtask. The time input via the source is not mandatory. But you have to make it mandatory either from the back end.

You’ll not be able to fetch the reports on the performance, the health of the project, capacity management, or IT management if the data is not input properly. So this is something which people most people don’t take care of as a Jira planning. But when you plan a project, you have to plan these things.

I rate the overall solution a seven out of ten.