Jira Reviews

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.

We use it mainly for Scrum management.

Most of the projects which we have taken in were using a waterfall model, which is very hard to convert into an agile or Scrum model. It helped our customers have visibility into requirements and reporting, since they were mostly using spreadsheets. We could help give them a clear cut view of what was happening on ground with development and the test database.

Reporting: It gives a nice report of my backlog and what my team has currently spent its efforts on.

JIRA still has their own backtracking tools. It should have a better visibility into HPE UFT. Most people use functional testing tools, like QTP. They need to improve their integration to make it seamless. 

You can do a lot with the tool but again, but it is not a 100 percent solution for everything. We have a lot of acceptance criteria coming through it, but JIRA doesn't support it. Therefore, we have go to different user stories and break them down. 

Using a cloud instance, it is always stable for us. It is not a problem at all.

We use a cloud instance for most engagement, so scalability has not been an issue.

My company has a 100,000 people, so we always can find someone within our organization who can help fix an issue.

I was not involved in the initial setup.

I understand JIRA is quite expensive.

Most important criteria when selecting a vendor:

1. Usability: It should be easy to use. People should not have to undergo a lot of training because it should be intuitive.
2. It should be scalable and a cloud solution. 
3. It should not be expensive. Cost is a major driver because I work in pre-sales.
   

I have worked with Jira for agile scrum projects. Jira is a good tool that helps you track and monitor all your stories, scrum updates, and Definition of Doneness (DoD). We can track everything we need to track and pull the reports from the Jira tool. Based on the team's activity, we can monitor, track, and update the tasks we have assigned through Jira. We also use Jira for sprint planning.

The most valuable feature of Jira is the reporting feature, which allows us to track our team's tasks. You can export and play around with the reports. In the defect tracking tool, you can pull the data and generate reports with a nice graph. It's very user-friendly. The solution's user interface is intuitive and easy to use.

Sometimes, Jira becomes slow when more people use it. Then, we have to close it and log in again. The solution's stability could be improved, and it could be made more robust.

I rate the solution’s stability a seven out of ten.

Around 2,000 users use Jira in our organization.

I rate the solution an eight out of ten for scalability.

The initial setup of the solution is very simple. You can install Jira as a standalone solution. Deploying the solution on the cloud is very, very easy, and then you can access it from anywhere on the cloud.

I have used Micro Focus Quality Center, which is purely a defect management tool. We can also use Jira as a defect management tool. When you compare both tools, Jira is now the best tool for defect management and running scrum projects. You can even expose the Jira APIs to do automation.

If you find a defect, you can automate the process of logging in to Jira and erasing the incident. When you find a defect while running JMeter scripts, you can take the APIs and automate it to save time. The automation process can be done through Jira because it exposes its APIs to third parties to integrate with other tools.

You can expose Jira APIs and integrate the solution with other tools. You can have your own dashboard using the APIs. I would recommend the solution to other users.

Overall, I rate the solution an eight out of ten.

My company uses the product for the user storage it provides. The tool is also useful for requirements management and test management processes. The product is also useful to track the hours people in the company have spent on testing and test logging.

The solution's most valuable features revolve around the dashboard view, which has a burndown chart indicating progress. I also like the tool's ability to provide details phase-wise, allowing users to see how many tickets are in development and how many are in the testing process. It also helps users see how many tickets are ready to move to the production phase. The aforementioned areas of the tool are pretty frequently used.

Some of the customizations are definitely a little challenging. I depend on Zephyr to manage certain reporting aspects and deal with the challenges of customization. More than a thousand records are something that our company cannot retrieve, but with the administrator's permission, the limit can be increased. Some of the functionalities to increase the limit of retrieval, in case there are more than a thousand records, could have been included as a default feature since it would be helpful if I wanted to do some analysis or if I wanted to extract all the details when my limit is only a thousand records and then I have to search for another way to find and extract the details. If the aforementioned details of the issues in the product are addressed, then it would be great.

If there is a provision to increase the number of records retrieved, it would be really helpful. In the tool, only a predefined reporting is there, and it helps with some of the more customized reporting, like Power BI Report Builder, so the area of reporting can be enhanced and it can be really helpful.

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

Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution a nine out of ten. The product is always up and running in my company, and we have not experienced too much downtime in Jira, making it a very efficient tool.

More than 50 people use the product in my company.

I haven't had the opportunity to interact much with the product's technical support, but based on the inputs from the other members of my team, I can say that my company was able to get support from Jira whenever required. I rate the technical support a nine out of ten.

Positive

The product's initial setup phase was not very complex, as it is manageable.

The solution is deployed on the cloud.

Compared with Jira, I feel Microsoft ActiveX Data Objects (ADO) is coming up pretty fast in the market since the features attached to the paid version work well. Microsoft ActiveX Data Objects (ADO) can easily integrate with other Microsoft products without needing any customization. Microsoft ActiveX Data Objects (ADO) is growing pretty fast in the market.

My company uses the product for planning tasks.

The product has played a major role in helping my company in the area of bug tracking. During the testing phases, be it SIT or UAT testing, if there were any issues, our company used to log the bug using Jira, and then we connect with the respective users, so we have a track of which particular bug and check to see if the bug is related to which user storage.

Jira helped our company's project management, analytics, and reporting parts. If you look at the analytical part, my company used to get the hours we have availed each of the user storage. When it comes to the user storage part, my company would like to see whether the hours we consumed were optimal or if it was over-consumed, which is information that we track with Jira. The tool is useful for tracking progress and seeing where my company stands when it comes to tickets. Each ticket might have a certain due date, which the company gets to see using Jira. Altogether, the tool helps users eventually understand the team's progress, the current sprint details, and how much of the team's capacity has been used. With Jira, my company gets to see the aforementioned details, so we were able to track it with the product's dashboard.

I am not used to using the product's integration capabilities with other solutions.

The product's user interface is good.

I recommend the product to others who plan to use it.

I rate the tool a nine out of ten.

We primarily use the solution as an ALM, an application lifecycle management tool. 

I like the entire workflow customization, which we could set up for our usage.

There are some really great in-built reports.

The solution is stable and reliable.

The scalability is great.

In terms of the initial setup, the solution is easy to implement. 

We've had zero issues with the product. It's been great.

Even though I like the reporting part, we have some issues. I don't know whether there is a Jira problem or a test risk problem, however, sometimes, we face issues on fetching the reports. This is when in-between integration comes into the picture. There could be easier integration. It used to be easier in 2016.

We've been using the solution for more than three years now. It's been a while. 

The product is reliable in terms of performance. It's stable. There are no bugs or glitches. It doesn't crash or freeze.

The solution can scale well. If a company needs to expand it can do so. It's not a problem.

We have 250 or more users using the solution. We might go up to 300. It's not likely we would pass 400 users. We might increase the usage a little bit.

We've never had issues with Jira and therefore have never reached out to technical support. I can't speak to how helpful or responsive they would be.

We used to use TFS.

The product is quite straightforward, especially since it is on the cloud. It makes it very easy to set everything up.

We have three people able to deploy and maintain the solution.

We did not use an integrator or consultant for the deployment of Jira. We handled the process ourselves. 

We pay for a yearly license. 

We primarily use the solution ourselves, as customers. 

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

I would recommend the solution to others. It would be ideal if it offered better tool integration, however, other than that, we've never had issues. 

Our primary use case of Jira is for tracking corporates and for new test cases where we need to execute monthly releases. We use it for test management purposes, whether for tracking or test use cases in their different cycles. We log everything on Jira and are very dependent on it. We are customers of Jira and I'm senior quality assurance person.

We've seen a benefit from the tracking of the release sizes and their status, it's very clear and simple, and the UI for Jira is easy to understand. 

Jira has a good dashboard. If I'm running an automated test script on different levels, say API automated or UI automated, and want to track automation status in the dashboard, I can get the overall status. I know how many cases are automated with the API or the UI and how many cannot be automated. It's a good feature. 

Jira could be more user friendly. When I started using it, I faced difficulties in different project selections and there were issues with bugs. It was not straightforward. I feel it could offer an improved user experience. I have a small issue that whenever I log out there's a bug and for a fraction of a second, I'll get a notification that then disappears before I can do anything about it. 

I've been using Jira for quite some time. 

From a performance perspective, I have faced many issues, some bugs and glitches, and there has been some down time. In general, it's a stable solution. 

The solution is scalable; we have BA, QA and Dev Ops people all using Jira. Everyone has  access, but certain users have access to certain areas. It's our test management tool so we use it a lot, everything is tracked on Jira and our reports come from there. 

We haven't used the technical support.

I used TFS before Jira. They are similar tools but I found TFS to be a more complicated solution.

The deployment took a few hours, some aspects were more complicated than others. 

I'm not involved in the licensing aspect. 

I rate Jira seven out of 10. 

I am working on a project which involves moving Jira onto the Azure boards. We use Azure DevOps for our repository and pipelines and we are looking to move on to Azure boards from JIRA for our ticketing or change request management.

Jira has helped our company because the board layouts are easier to use and has helped us see what is happening in regards to stories and bugs.

The layout, workflow, automation, and metrics are helpful in Jira.

The flexibility of defining your columns that can possibly contain multiple statuses is important. When you have teams that are different levels of granularity, the C levels, only care that it is in progress, but the leads want to know that it is in QA or development. You can accomplish these types of things with JIRA.

The biggest complaint industry-wide about JIRA is they need to purchase additional extensions, such as reporting automation. If they could provide some additional extensions from the initial purchase it would be a huge benefit.

When using the service desk and the developer, the transition could be better between the two. For example, we asked the support desk to send a ticket over to the development and it was a little bit cumbersome. We had to recreate another ticket for development, then we had two tickets, one service desk, and one development. It would be beneficial if the process was more smooth between those two packages.

I have been using Jira for approximately eight years.

The stability of the cloud version of JIRA is very good. However, we did have some issues with the on-premise version but the issue could have been because our servers were overloaded.

The scalability has been very good.

We have approximately 40 people using this solution in my organization, which is mostly everyone. It is used by many departments, such as project offices, development, and coding QA. The only department that is not involved in the use of the solution is the company support. I had worked at a company previously that used the JIRA service desk for their support and it worked well.

I have previously used DevOps and Rally.

JIRA installation is complicated. It is similar to a lot of other systems, the more flexible they tend to be more complicated they become.

We do the maintenance of the solution which is adding users and moving them around. The solution is very hands-off, it does not require a lot of maintenance.

We currently are evaluating other options and are doing a study to see if we are going to continue using JIRA or move to something else.

I would advise those wanting to implement this solution to contact an expert. 

This solution is a top-of-the-line CRM, I have used the others solutions, and it has the most flexibility and the best visibility.

I rate Jira a nine out of ten.

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

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

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

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

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

I have not seen any issues with stability or scalability.

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

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

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

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

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

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

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

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

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

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