Jira Reviews

We use it for backlog management, sprint planning, requirements management, Scrum, conducting Scrums, and all of our agile stuff.

It handles all of the issues that we need it to do.

It is very flexible, so we can do pretty much what we want with it. 

I would like integrated requirements management, so we do not have to buy plug-ins for JIRA, since it was hard to get requirements management for it.

It is stable.

It scales up well.

We have a team who administrates technical support. They handle this interaction with JIRA. Sometimes it takes a while to get a solution, but they solve everything. 

Before, we used a homegrown solution. 

Almost everybody uses JIRA nowadays because it is the most cost-effective solution.

I was not involved in the initial setup. 

I do know the initial setup was pretty complicated. The user interface could be better organized and easier. 

It does not cost that much.

We did not really evaluate anything else. All of the other products were way too expensive for our purposes. Also, JIRA is the de facto standard.

It is very capable, but also very complicated.

Most important criteria when selecting a vendor: reliability.

User friendly, easy to set up and maintain. Great integration along other Atlassian tools. Application can be enhanced either with free plug-ins or you can create your own.

Seamlessly merged efforts between quality and R&D.

Missing a Requirement Management piece on the suite.

We use Jira primarily for Agile development and change management.

The most valuable feature is its flexibility. There is flexibility in the structure, lifecycle, and workflows that you want to work with.

The interface is user-friendly.

I would like to see more robust release management within the tool. We're not able to use it at this time because of compliance issues within our industry. At this point, I'm not confident that it can meet the requirements.

I have been using Jira for about two years.

This product has steadily improved since the time I started working with it.

I would rate this solution an eight out of ten.

Maintained by a big company. Simple installation process. Extremely customizable. Front-to end exposure (repository, issue tracking, feature management, etc.). Enormous user base with lots of exposure. Add-on plugins. Excellent documentation and support. We can take advantage of the 10 user certificates of confluence and green hopper. Will be good to use when the project is going to start.

Generally, customization, granted that it is done only at system productions state, is hard and time consuming. Most of functionality that is not required for use of system, cannot be deactivated; you need to dig through all superfluous stuff, in many cases. Even though JIRA documentation is immense and solid, filled with tutorials, you really need docs, to use JIRA, the system is so complex that you need to read docs almost for every customization task and even then, some views are hard to understand.

I'm a consulting company. I provide solutions for many companies, and in some cases, I implement Jira. DevOps is something else that I provide for my clients.

Our clients range in all sizes. I have microscopic clients, such as a one-man company, and on the other end of the spectrum, I have the New Zealand government, for example.

The most valuable feature of Jira is that it's a well-known tool that many people are familiar with.

Jira is not the best tool; I just don't like it.

I am not looking to improve Jira. I have transitioned to using Azure DevOps or GitHub.

I don't like the interface or the way it is structured. I prefer the way it is done in Azure DevOps.

It is not user-friendly.

I have been acquainted with Jira for approximately five years.

Jira is a stable solution.

I have not contacted technical support.

We are also providing Azure DevOps.

I would recommend DevOps because it is more user-friendly and easier to use.

I was not involved in the initial setup of Jira.

I would rate Jira a five out of ten.

Public Cloud

We mainly use the solution for project management. We are using Jira for our software development purposes only. Usually, we create a Jira project for each project and develop it according to its size. We assign team members who will belong to those projects, each project. Then, we manage everything using Jira.

Basically, the main purpose of using Jira is just planning and then checking issues. That's all for now.

We can lean on Jira completely during projects, even in terms of all the small things, surrounding planning. There are error reports, and we can take in the progress. We are not using any other tool except Jira for managing software development, including the testing and reports and following up.

Overall, the solution is very nice and has a variety of great features. 

The stability of the solution has been quite good.

We haven't had any issues with scalability.

It's a very useful project management tool.

For me, the solution is too complicated as it has too many features. It would be nice if they could streamline things.

They can make it a little bit better in terms of the user interface. Some things are very scattered. It is a bit confusing. They developed a new user interface, and I cannot follow the changes. There's documentation, however, it's not so good.

The solution has a pretty steep learning curve. It would be great if they could lessen the learning curve by providing more templates and ready-made options for new users to take advantage of.

I've been using the solution for almost two years. It's been a while.

In terms of stability, we haven't experienced any crash or anything like that. There are no bugs or glitches. We haven't suffered any issue with the Jira service itself so far.

Due to the fact that we are using the cloud service of Jira, we don't have any experience with any lagging or delaying or any of those kinds of issues yet. The team is managing this scalability and can scale up and down their resources automatically in the background. I don't have any issues with the scalability that's provided.

We are a small organization. We only have a team of 20 developers. We might increase usage in the future, should our team grow.

We haven't had to reach out to technical support just yet. I can't speak to how helpful or responsive they are.

I wasn't directly involved in the implementation process. I can't speak to what cloud the product is on or the exact details of the deployment.

We have only two people for the Jira management. We are only paying attention to security. We ensure we are giving the right permission to the right person, that is the only factor we are focusing on. 

We are just customers and end-users.

As we are using the cloud version of the solution, we are always on the most up-to-date version.

For simple project management, Jira is too much. If you want to manage a project precisely, however, then I can recommend Jira. It's not only a software-specific version. There are different versions of Jira so that you can apply it to different areas - not just software. That is one good aspect. I'd say that it is very polished, and has a very well-defined approach to project management. 

I'd rate the solution at a nine out of ten. We've mostly been happy with how it's worked for us.

Public Cloud

We use this solution for our scrum team and user story management.

This solution assists us with being able to quickly and easily start sprints and keep accurate track of them, including billing using a time-tracking add-on.

This solution is very easy to set-up and use. It is very intuitive.

The permissions can be challenging to get right.

We have been using this solution for five years.

• Running agile deliveries with dispersed teams. 
• The projects were typical agile, changing requirements frequently.
• JIRA facilitated story management perfectly.

• Overall, it has good viability. 
• Relatively easy for everyone to pickup and use. 
• It improved communication, as it was a popular tool, and most people enjoyed using it.

Kanban board: The board is easy to use and visually impressive to non-IT users, who found it easy to relate to.

• Report customisation could be improved. 
• Out-of-the-box reporting is limited. It would be helpful if more customisation was possible.

One to three years.