Jira Reviews

The primary use cases for this solution are backlog management and sprint planning. Customers deploy this solution on-premises. 

The two features that have been most valuable have been backlog management and sprint planning and tracking. 

This solution could be improved by including a different model for the overall planning perspective. There's a Jira portfolio that we aren't using. The only challenge we're facing is that we cannot see the overall planning. 

I have been using Jira for almost three years now. 

This solution is stable. On-premises, the stability is okay, but when it's cloud-deployed, I think it will be more stable. 

This solution is scalable, but I think it will be more scalable when we go with a cloud deployment. 

I have never contacted support directly, but our team that takes care of maintenance, support, and customization connects with them. 

I previously used Micro Focus ALM Quality Center for around five years. 

Installation was done by someone else. For deployment and maintenance, we have a DevOps team of two or three. 

I implemented through an in-house team. 

We don't pay for licensing because we are using the Open Source version. 

I rate this solution an eight out of ten. I think it's much better than other competitors' products. 

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 primarily use the solution for all issue reporting. The business uses it and we use it in IT as well. Any issue, anything from the help desk to software issues use Jira. It can house test plans, test sets, test executions, and provide some reporting. It's the reporting that's important for us.

The product has formalized the workflow process for reporting tracking and stacking and processing issues. It's also added some formal approvals, just for the purpose of formalization of a process workflow.

If you're using it in an agile shop, the traceability between epic story's test case defects is very helpful. 

I like that all of the team members on an agile team can use it. No one is in a separate application.

The stability is good.

The product can scale, so long as you have storage.

The reporting needs to be better. Being able to do some test management would be useful. In the tool, it would be ideal if they could give you some out-of-the-box reports for things like requirement coverage and regression and things of that nature.

I've used the solution off and on for about four years. I used it when it first came out to do some evaluation and we implemented it at a startup. That was when it first started. I've probably only really used it for about eight months on a daily basis.

We have had no downtime, and therefore I don't have anything to say that would be negative. It seems to be quite stable. There are no bugs or glitches and it doesn't crash or freeze.

As long as a company has the money for storage, it's scalable to any size. A small company can use it or an enterprise-level company can use it. It works for both.

Currently, we have less than 1,000 users in our organization using the solution.

Jira is extensively used in our organization.

We do plan to increase usage as well. The company purchased it so that it would be scalable. There's not a solid plan right now to add measurable users or increase the size, however, we know that it's available and that's what we were looking for - something that is scalable. The plans are to grow and as that growth happens, either organically, or via the purchase of other financial entities, we can grow the size of the database application and the number of the users.

I did not personally use technical support. I have worked several months with the people who have, and they say that the support is very good.

If the company used something previous to Jira, it was before my time. It possibly could have been Sharepoint, however, I was not with the company at that time.

The solution was implemented before I came to the company.

That said, my understanding is that the company tried to use as much out-of-the-box functionality as possible and it was quite an effort. They spent quite a lot of time formalizing workflows and things of that nature. In the end, it was very well thought out.

We do have a team for maintenance and what takes the most time with any upgrade is going through the changes, the enhancements, the defect fixes, and things like that. The actual time that it takes to physically update it is pretty minimal. However, going through the documentation and meeting with the team to make sure that we have testing covered prior to upgrading is work. We have a test environment prior to pushing it to production. That's what really takes time. It's not the physical update. An update might take two and a half hours and there's a lot of data in there.

My understanding is the company used professional services from Jira and also got some training and stuff of that nature.

We're just customers and end-users.

We just upgraded the solution. We are on the latest version.

I'd advise potential users to make sure that they talk to the people who are going to be testing and make sure that they know, what metrics they need before they pick a tool, any tool - even if it isn't Jira.

I'd rate the solution at 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

We are using primarily using Jira for the project and issue tracking mostly.

One of the most valuable features is querying because the jQuery function is very good. Additionally, we can create good designs very easily.

There are too many restrictions in Jira. In DevOps, you can access the dashboards easily, but in Jira, you should have more administration rights. In our organization, there are some restrictions on creating dashboards and other features. Everything should be accessible with all access rights for everyone.

Jira should allow you to create and develop pipelines easily. In India, we have to purchase them separately or integrate other data tools. All these tools should be in Jira.

I have used Jira for approximately 12 years.

Jira is stable.

In my experience Jira is scalable.

The technical support has been satisfactory but could be better.

I have used DevOps and the main difference between DevOps and Jira is the test cases. You can have test cases in DevOps, but not in Jira. This is what I have observed in my recent comparison. Jira has jQuery and it is far better than what they have in DevOps. There are some filtration and grouping settings in DevOps which I do not like.

The initial setup is easy.

Jira is expensive and a lot of people are choosing DevOps because they are cheaper, open-source, easy to use, and have basic licenses. Jira should decrease its price to be more competitive.

I rate Jira an eight out of ten.