Jira Reviews

We are using Jira for requirement and defect management. Not for DevOps purposes, only application development.

The dashboard and reports tracking and the setup updates quickly, I am very impressed with those features. Additionally, it is user-friendly.

The integration of Jira could improve. The solution should be able to integrate easily with other solutions, such as ERPs. There are times the solution can be slow and we have to reset it over and over again.

In an upcoming release, they should improve the user management features. For example, when I want to monitor a project as a CEO I do not want all the details but enough that I can understand. Additionally, these features should be accessible to me by mobile.

I have been using Jira for approximately two years.

Jira is a reliable solution for that medium-sized organizations. It's not for enterprise-level organizations, they have a long way to go.

The scalability has to be improved more because Jira currently is similar to a standalone solution with very limited integration. The integration with other products has to be more.

We have approximately 50,000 people using the solution.

We use our own IT department for the technical support of Jira.

The initial setup was complex.

We used to be on a perpetual license provided by our clients.

I would recommend this solution to others. Any new startup company can start with Jira immediately because it is now offered in the cloud.

I rate Jira a nine out of ten.

As a lead consultant, I assess the testing maturity and suggest how our clients can improve what they're doing. I also carry out training sessions for Jira and other solutions as to how they can effectively use the solution. 

I like the ease with which we can do our workflow administration, especially with respect to defects. We can do good work with the boards, whether it's a Kanban or a Scrum board. It's much easier with Jira than with other tools. 

The solution could be improved with respect to how the end-to-end is managed from product backlog creation until test completion. Although it can be customized, if there was a standard out-of-view box feature or a workflow, that would be helpful. There are features that are currently not out of the box and lack end-to-end traceability, such as the business value of a particular feature. It would be great if that were included. 

I've been using this solution for over two and a half years. 

The product is stable. 

We are currently working with an enterprise client and we are able to scale easily. 

Jira's technical support is good. 

I previously used HP ALM, as well as TestRail, which is now focused more on test management. ALM was the major tool that I used before we started using Jira.

The licensing costs are reasonable. 

This tool has good capabilities but you really need to know what you want to do and freeze down your requirements before using it. It can be challenging when people don't understand the difference between Kanban and Scrum, and how you use those boards effectively. 

I rate this solution eight out of 10. 

We use JIRA for the management of tasks in IT. We are in the process of implementing our JIRA service desk and using other software for development, such as Bitbucket.

When combining Jira with Bitbucket, you have the possibility to ensure continuous integration and other functions which is highly appreciated by our software development team.

I have been using Jira for approximately three years.

Jira has been stable in my experience.

The solution is scalable. The new licensing model that was presented to me for the data center oriented solution, the price tag that comes with it is the equivalent of 500 users. I only have 50 to 60 users, which means that I have to multiply my budget by 10. This is the scalability that they should be able to provide and I do not like that too much. I can accept that there is a markup for the data center but not the way they have currently presented it.

We will have approximately 60 people using the solution and when it comes to the software development team there are approximately 100 users. It is used in two separate environments.

I have not contacted technical support personally.

Before we used Jira, our operations were very Microsoft office-based.

I am not a regular day-to-day user of this solution and based on the feedback that I received from people at the time it was installed, it went well.

We have one person from an external party who helped us with the implementation. For the internal technical deployment, we have approximately five people from different teams in infrastructure, help desk, and application.

The price at the moment for Jira is okay. I'm absolutely not amused with the plans to try to drive us to the cloud or to other licensing models. For the very simple reason that we are a company in the defense sector where cloud is problematic in a number of the domains. We are now approximately 60 users and the new policy will actually confront us with an upscale to approximately 500 users. I find it unacceptable, and may potentially lead us to look for another solution.

They need to think about industries, which are for compliance reasons are not capable of moving to the cloud, and that they don't put a knife on our throats with excessive prices.

For my defense software development activities, I would like to stay out of the cloud. For the general industry activities and the IT support, we could potentially go into the cloud. There is no objection to that. But for defense, the cloud is not an option for me.

If you want to move ahead to the cloud, I would definitely recommend Jira. For what we use it for since we are stuck on-premise, I would advise others to look into other solutions.

I am not an active user of Jira but based on the feedback I have received I rate Jira an eight out of ten.

We are using Jira Interview to handle all the facts from clients and schedule calls with them. We have a different operations department that configures Jira, and we have technical people that help us choose the deployment model. 

The main reason we are using Jira at this time is for a different dashboard and chart. The major one that we are using is for the stock analysis, and it's nice to get that time log for our team, get the score of the game, 40 points delivered in a week or a month. we are using Jira for following purposes:

Issue tracking
Customizable workflows
Estimation & work logging
Progress reporting
Scrum boards
Kanban boards
Project-level permissions
Project backlogs
Email notifications
Roadmaps

Productivity increased by using this tool and organization can measure the productivity of a resource. early alert being displayed in the case of project failure and success. Org can identified the work load on resources for a day. 

We like the test cases in Jira. The orange dash items view was great, and we like the features and layout of the data. It's quite different, and people are now getting their items so quickly. We love the bulk edit feature. Jira also integrates well with Bitbucket.

Sometimes it takes time to load the data.

I've been using Jira since 2015.

Performance-wise, Jira is good, but sometimes it takes time to load that data. 

Jira is scalable. We have about 470 people working with Jira in our company.

The support team is very helpful and supportive. I requested multiple things and faced some concerns, they were very cooperative and responsive.

Asana. Jira has better work flow and features relative smart and easy to use.

It is easy to set up. We can use project templates. We can use classic projects templates or create new templates. We have also build the custom workflows for the custom templates.  We use templates for our daily progress.

I would tell potential users that they should all get it.

On a scale from one to ten, I would give Jira an eight.

I'm head of the IT service desk, and we're using it to track IT tickets from the users. If there is an incident or someone requests information or services, we handle all these requests through Jira Service Desk.

Jira is flexible and accessible for the end-user. It lets users track their requests. The look and feel are good for our purposes. I'm the IT service manager, so I'm like the director. A cleaner interface helps my team stay on top of the service requests. We used to just take requests via email, and we had some kind of old IT tool, but it wasn't as effective as Jira. And because we are connected to Power BI, we have better visibility. You have a range of metrics so you get some good insight when you integrate Jira to Power BI.

My colleagues started dealing with Jira in 2019, and they're still using it. And my team implemented the Jira Service Desk in 2020 because the rest of the company was using Jira.

Stable. What about scalability? Is it scalable?

We get outstanding technical support through our partner Valiantys, which is a French Jira distributor certified by Atlassian to resale Jira.

It's not a complex implementation, but it's not easy either. I think it's somewhere in the middle. It's an average software implementation.

Jira is raising their prices for the license, which is like a trap because many other providers offer services like Jira but for much cheaper. And now they are making us move to the cloud. They gave us a deadline to migrate from the on-premise Jira Service Desk to the cloud. It's been two years since we started using it, so I think we will get a discount.

I rate Jira Service Desk seven out of 10

The way it interfaces with Bitbucket and other things like that is valuable. Reporting and being able to link various issues or stories together are also valuable. We call them stories, and they're general reports.

I never had an issue with it at all. Everything I needed to do was always there. Everything is cool.

It should have Behavior Driven Development (BDD). There should be an option to add macros to help with that. A lot of people are using it now, and it would be nice if there was a way in there to be able to generate the BDD of commands whenever you're creating a story.

I have been using this solution for probably 8 to 10 years. I have used it at different companies. Cloud is the way they had it set up.

There were probably about 600 users, and they were from top management and all the way down to the testers. So, pretty much everybody used it.

I would rate it at least a 9 out of 10. That's because I never had any issues with it. It always did what I needed it to do.

We use Jira in our organization for lifecycle management.

The solution has helped our organization do lifecycle management easily.

I have found the most valuable features of Jira to be ticketing, life cycle workflow, definition, and creation. Many of the features are useful.

The solution could improve by having its own tool for quality lifecycle management.

I have used Jira for approximately nine years.

The stability of Jira is good.

Jira has good scalability.

We are using this solution extensively. We have more than 5,000 using the solution in my organization.

We have been satisfied with the technical support from Jira.

We have used in-house developed tools previously and we had to do a lot of customization and this is why we moved to Jira.

I would recommend this solution to others, it is a good option.

I rate Jira an eight out of ten.

It is helpful for bug tracking in software development. If developers are doing some work and testers notice some defects, they can flag it in JIRA. For example, I track my day-to-day work in JIRA so that others know what I'm working on. They can look at JIRA and don't need to contact me. From JIRA, they can find out that I am working on this project and spent two days on it, etc. It's used for so many things, like task management, bug tracking, and release management. 

JIRA is not for deployment. For deployment, you are going to use some tools like Jenkins. It's meant for all the features that are going into that deployment. 

Different teams within the company use JIRA. For example, everybody in the engineering section uses it, so altogether, that's around 200 people.

JIRA gives us a lot of visibility. For example, if you're planning to release a given feature, you can track the status of that feature. Is it working correctly, or does it have some bugs? So you have a high level of visibility on the work. 

The JIRA user interface looks great. It's an overall good experience. It's very intuitive in the sense that you understand how it's going to work. It's very self-explanatory, and it's beneficial overall. Each release has different steps and phases, and the whole thing can mostly be captured on JIRA. The workflows are really helpful. 

So at one point in time, they did a huge UI upgrade. At that time, I felt like they had changed something, so it was hard to figure out. Now that we are habituated, it's not an issue now. We had gotten used to the old interface, so things changed, we felt an initial discomfort. That's the only thing. Otherwise, there is nothing I dislike about JIRA.

I've used JIRA since the beginning of my career and nothing else.

I haven't had any issues with JIRA's stability so far.

The scalability of JIRA has always been good. The response time is always fast. I've never had any issues with scalability. I think no matter how much our usage increases, we'll continue to use JIRA.  But, I think our usage is at an optimal level. 

From our end, setup is basically book-keeping. I can't say much about the overall setup because there is an administrator for JIRA who adds users and sets everything up. I haven't been an administrator. I'm just consuming the JIRA. 

Initially, I think administrators are going to set some things like configuring the workflow should and then how you want to say things. But other than that, if you set it up once, it's going to work. You don't have to do much maintenance.

I rate JIRA nine out of 10. I would recommend it.