Jira Reviews

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.

We use it mainly for logging defects and tracking them.

The UI is good. It's simple and not very complicated.

It's very good for tracking.

The thing I don't like is that it is hard to decide which dropdown options should be selected. When we try and submit it, it will state that there are certain mandates in place. It won't allow us to submit the form unless we fill out all the details.

I don't think Jira has a copy/paste option for emails. I know that you can attach emails, but I don't think there is a copy/paste option.

I've been working with JIRA for the past 10 years.

I would recommend Jira because it helps from a functional point of view and also with tracking defects. It is similar to Quality Center and is good.

I would rate it at seven on a scale from one to ten.

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.

Our company follows the Agile methodology for software development, and this product is one of the best tools for companies that do so.

We regularly check the tasks assigned to us, day by day, and create a work log in that task according to what has been done.

You can check today's task assigned to you by using a custom filter, which you can create on your own. We can also make a customized dashboard user-wise.

Upper-level management can analyze the chart and get an overview of the project, giving them the ability to estimate the budget and release date of the project.

After purchasing Jira, we started shifting to it from the older software we used, like Bugzilla. Bugzilla was being used as our bug reporting tool but after the introduction of Jira, we began to use several of its features. We now use Jira for Scrum Planning, Bug Reporting, Time Tracking, and Budget Tracking.

Day by day, the transparency of the project improves and estimating the project release date becomes easier to do. It is also easy for management-level users to check the project's budget and estimate the release date for a specific feature.

Because there are a number of charts available, looking at them will assist you with any decision that is related to your project.

As a user of the Jira, rather than an administrator, the custom dashboard and custom filter are some of the best features from my perspective.

I can manage my own dashboard and by logging into my account every day, I can get information about the day's tasks assigned to me. I can also see my timeline chart, and using that, I can see and understand what has been done in the last week/month.

I have added a gadget on my dashboard that gives me regular updates on the bugs reported by the QA team.

Jira is one of the best software applications for project management and budget tracking, but it does have some issues, as follows:

• Firstly, the filtering feature can be improved to some degree.
• Because JIRA has so many features, it may take some time to obtain a general knowledge of each one.
• In order to enhance adoption in small and medium businesses, the cost should be improved.
• I believe it will be difficult for new users to understand.
• There are a limited number of gadgets accessible in Jira; thus, additional ones should be supported.

In our organization, we have been Jira since 2017.

Previously, we were using the Bugzilla bug tracking software for reporting bugs from the QA and FITs. Due to the number of problems that we had with it, we purchased Jira and have been using it for approximately five years.

The initial setup was easy, and we haven't found any difficulty in that.

The pricing is much higher than other similar solutions available in the market, and as such, the vendor should think about a price reduction to make this product more affordable.

We did not evaluate other options before implementing Jira.

Our testers and QA teams use this tool. 

This solution is easy to use and takes a lot of burden off the QA team.

I'd like to see a more stable product with more integrations, as new products are coming on the market daily.

.

The technical support could be better, a little more customer friendly and knowledgeable.

The initial setup was quite straightforward. We had our technical team deal with it. We currently have around 25 people using the product. 

We pay an annual licensing fee. 

I rate this solution an eight out of 10. 

Our primary use case is for project management, guiding the teams in our company. The solution allows you to create Scrum boards to deliver all the acquired stories within the Scrum Sprints. It also adapts to any other Jive methodology, like Kanban, and helps the creation of roadmaps for the software, production and implementation. We use it for day-to-day tasks, managing our stories, assigning tasks to different developers, and even integrating it with other system control tools to link the story's details. We are customers of Jira. 

The Jira user interface is really helpful because you can see the big picture regardless of what stage the task is at. You can define priorities and estimate times. If, for example, you're planning to move to Scrum, you need a project management tool; JIRA is perfect for that. It can also be used on personal projects because they offer a free plan with unlimited features to manage your project, define your backlog, and check the status of a project. 

The solution comes with multiple reporting charts so you can see the sprint burndown chart and other information. We previously had our own internal tools for Scrum, and moving to Jira was a total upgrade. There's no need to create new accounts for your users. You integrate company emails with an internal server, grant the user access and with their  company credentials, they can log into the platform. That's a pretty good feature. 

They could probably improve the integration with some of the automation tools and provide a specialized user interface suitable to their requirements. 

This is a very stable and reliable solution. The whole company uses it and we have around 500 employees. Our team adopted Jira recently but others in the company have been using it for a while. 

Jira is very scalable and allows for the integration with source control tools.

I haven't had to contact technical support. 

The initial setup was straightforward, we got access to it and started using it. They also provide you with documentation which helps if you are new to Scrum and new to the platform and features. 

There is an annual subscription fee based on the number of users. You can get a subscription for just 10 users, for small teams, and if you want more you can buy more. They have a standard and premium license. 

I would definitely recommend this product because it's scalable and easy to use. They provide best practice articles and quick start tutorials which are very helpful. If a new user has all the documentation, they can go from zero to hero very quickly.

I rate this solution a 10 out of 10.  

We using this solution to handling all of our development and support tickets.

We have found the structure, functionality, and how Jira handles the tickets most valuable.

The performance could be improved in the future.

I have been using this solution for approximately four years.

We have had some issues with stability.

The scalability is good for what we are using it for. We have approximately 20 people using the solution in my organization and we plan to increase usage.

The technical support could be more responsive.

We have one technician handling the deployment of Jira in my organization.

There is a monthly license required for this solution and it is expensive.

I would recommend this solution to others.

I rate Jira an eight out of ten.

I'm working on creating test cases and one test. I also have an overview of the Sprint.

In general, the GUI is nice. 

The part when it comes to the testing area is a bit hard to handle. The screen is too small, you can't really read what you're typing in, and it's only for the testing area. It looks like they have pressed in more than the UI system could handle to display it properly.

I have been working with Jira for about eight months.

Jira seems like a stable product, but sometimes I'm losing data.

As a totally different team does the entire setup, I don't know if it's scalable. But we have about 150 users.

To be quite honest, at the end of the day, a tool is just a tool. For me personally, it's hard to say this tool is much better than the other. From just what I know so far, Micro Focus Octane looks a bit more modern. But I don't know which Jira version we're using at the moment. Octane looks a bit more integrated, it looks a bit newer, but would I buy a tool because of that? Certainly not.

I would recommend Jira for Sprint management. But when it comes to documentation of manual tests, I would say, "Okay, you can buy it if you want to have one package, but you can also have a look at something different."

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