Jira Reviews

We are using Jira for our test management. We're using it to record our inspecting results and to regulate the evidence in the report. 

The integration could be better in Jira.

I have been using Jira for approximately 15 years.

I have found Jira to be stable.

Jira has been scalable.

There is an annual subscription to use Jira.

I would recommend the solution to others. I have been happy with Jira.

I rate Jira a seven 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 software management. 

I really like the linking and user stories, and the formatting on the solution. The formatting options and linking the user stories have been great. 

You can export the whole backlog if you want to - including your roadmap.

The initial setup is easier than the TFS.

The UX and useability os good, especially if you compare it to a solution such as TFS.

You can use it right away without too much of a tutorial. 

The solution is stable. 

The scalability is good.

I would suggest Jira makes the format compatible with Microsoft Word. Currently, when you copy and paste something from Jira, such as tables, it won't be the same when you copy it into a Word file. There are formatting issues. 

If you have 70 or 100 stories, it doesn't work to copy and paste or export each one individually. There needs to be better configuration at a categorization level. 

There needs to be a way to export a user story. 

By default, Jira is epic and story only. It would be ideal if there was a different categorization between the two. It would be nice if there was a third story option. 

There should be a plugin for test cases. 

If the solution doesn't have third-party plugins for some features, they should add it into the main offering to make it more complete. 

I don't have a lot of experience. I only have about four months of experience or something like that. It's not a huge amount of experience, however, I got familiar with the basic features of Jira over that time. The first two months might have been on a trial version.

The solution is stable most of the time. Only rarely are there some points where it's not stable. For example, when you view some issues, sometimes it gives an error. Then, after that, if you refresh or you open it at another time, it may work again.

The solution can scale. If a company wants to expand it, it can do so.

We have more than ten people on the solution. 

If you need to find answers, the community FAQs are pretty good. I've found issues in there in the past that have helped me troubleshoot. So far, I'm pretty satisfied with that aspect of support.

The initial setup is straightforward and simple. It's not difficult or complex. 

I don't deal with pricing, billing, or licensing. I can't speak to the exact cost of the solution. 

We likely pay a licensing fee as we have more than ten people using the solution, however, I can't say what the exact cost is. 

I have been researching the difference between Jira and TFS, to decide what is better for our team to use. I'm very familiar with Jira. However, some of my team members have experience with TFS. I'm trying to decide which management tool we will use in an upcoming project.

I have found that, with TFS, a lot of the features are built-in, however, with Jira, you are required to add in plugins. 

I'm a customer and an end-user.

I would rate the solution at an eight out of ten. For the most part, we have been satisfied with its capabilities. 

I would recommend the solution, however, I would warn that likely a company will also need to add many plugins in order to get the solution to do what they need it to.

I believe we are using the latest on-premises version. 

Confluence, not Jira, is the most convenient feature with Atlassian. We use the product for knowledge management, the use of creating or documenting knowledge into a knowledge base.

I would like to have a future-proof idea of the cost and the roadmap for my class. This is in light of the fact that they are switching things up, promoting the cloud service and mixing different support levels.

The CMDB and knowledge platforms that are in the background of the ticketing tool should also be addressed. 

I have been using Jira for five years. 

When it comes to the question of stability, this depends wholly on the amount of resources provided to the virtual servers, since we make on-premises use. 

We have internal Atlassian experts, so it is tough for me to comment on the technical support.

The price of the solution could be lower.

We are currently in the initial stages of contemplating a switch from Jira. 

My advice is to work closely with Atlassian to make sure that all the designs are future-proof.

It is tough for me to Rate the solution. There are features needing improvement, but also many good things about Atlassian. As such, I rate Jira as a seven out of ten.

We are using it for service management, change management, project management, and tracking the changes.

It is user-friendly, and you can manage your project according to the methodology you want. It is also easy to configure.

The dashboard reports can be improved. Its dashboard reports are good, but you cannot have complex reports. They are currently very basic. For instance, we can only choose two columns for a dashboard, so it is not friendly enough.

So far, I've only used the project management parts. We are examining resource planning and sample plugins for the product. From my point of view, resource planning is a little bit hard to link with project management. Sample plugins are another part of the system, and we need to link it with project management in the BigPicture screen, which is a little bit hard. It would be valuable for us if we can do resource planning in BigPicture as well. Currently, it is another plugin, and you can only plan based on the people and not projects, and you cannot link it, as far as I know.

My company has been using it since the beginning of this year. It has been around six months. I have been using it for three weeks.

It is stable, and everyone generally looks satisfied.

We are trying to settle the project management part and widen it to all countries in our company. There will be many users.

We are working with a consulting company. Technically, we are okay because all of us are using it now, and there is no problem. We just need to see more details of some of the modules of Jira.

For its implementation and deployment, they have been working for one year.

Jira is a big platform, and you can use staff management, project management, and other fields that all companies want to use. If you use Jira, you will see the whole IT governance in one system.

With this solution, we can see the full picture in detail, but it can be improved. Resource planning is not easy for our project base.

I would rate Jira a seven out of 10. It will be an eight in the future. I need more time to work on Jira.

We use Jira product in the organization to automate the software development life cycle.

It's a very flexible product.

We can change the workflows as much as we need and we've done that already. 

The workflows are very easy to handle as far as scalability goes.

If there is a feature or a workflow feature, that is required and it's not available out of the box from Jira, from Atlassian, we have the marketplace buy from. There are a number of add-ons that we use. We have maybe 20 to 25 that fill in any gaps in the system itself.

The user interface is very detailed right now. It could be simplified if they consider targeting the user experience. Right now, on the screen pre-design, the amount of information on the screen is very high. The distribution is good, however, the presentation itself looks very technical. They should work to streamline the UI to make it better for users to digest the information.

I've been dealing with the solution for two years now.

The solution is very stable. We haven't had issues with bugs or glitches. It doesn't crash or freeze on us. It's quite good.

The solution is scalable in terms of the number of users and the number of features. The features we are using are mostly out of the box, however, we have added product management features and code delivered with the integration features. We also have added test management tools or add-ons to it including reporting and dashboarding as well. You can really grow it out and add as many plug-in apps and features as you want.

Currently, we have 500 users that interact with Jira within our organization.

We have good internal technical support for Jira in the organization and we use the Atlassian technical support only when needed. Thus far, we are quite satisfied with the level of support we receive.

I cannot give too much information about the installation, as we're similar to a consultant, and I don't want to get into too many details. As the installation engine, we took two days straight to deploy it and that is with the implementation.

For deployment, you don't need a huge team. We did it with two technical personnel. They are consultant level system administrators.

We're just a customer. We don't have a business relationship with Jira.

We're using the latest version minus one, due to the fact that it was installed year. That upgrade was last year and it is my understanding that there is another version coming up.

I'd recommend this solution to other companies.

The product is very scalable and it's very flexible to match any organization, however, the trick to using Jira effectively is that there should be a business process documented in place before using it straight. The mistake that many people do is they consider the tool as the base and they configure their processes according to this. If they work the other way around and have a great process between all cycles, and then implement that process on Jira, it's very beneficial.

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

The solution's most valuable aspect is its workflow sensibility.

The user and group management could be improved in a big way. There really are a lot of administrative areas that require a lot of screens which could be improved in many ways.

A lot of the user interface could be updated.

Technical support is lackluster. It could be improved.

They need to address a lot of the requests that people have had over the last 10 years. Instead, they rely on third-party tools to provide these features. They don't seem to understand what it is their clients really need and instead just assume a plug-in can be made for whatever the purpose is.

I've been using Jira for ten years. It's been a decade now since I first started working on the system.

The solution is extremely stable. There aren't bugs and glitches. It doesn't crash or freeze. It's quite reliable.

The solution is absolutely scalable. If an organization needs to scale up, they can do so easily.

Technical support is pretty bad. They rely on partner companies for support and don't really have any of their own internal teams that can help.

The initial setup is not straightforward. It's quite complex. However, you do tend to get used to the process after a while.

The solution is quite expensive. I'm not sure of the exact pricing, however, I know it's not cheap.

We're an Atlassian partner.

I'm actually using various versions of the solution. I stick with versions seven and eight, mostly.

I'd rate the solution seven out of ten.