Jira Reviews

Our primary use case is for our own network operations, and integrating via API with our customers network operations teams.

It created excellent data points and summary with up-to-minute information.

The informatics is the most valuable feature. It captures what we need.

The user interface could be better, but the stability is definitely there and the accuracy is good.

The GUI should have much better features like more graphical illustrations. There are some cases or benchmark data that we are trying to capture and customised into a graphical pie chart summary dashboard, but unfortunately JIRA is not able to do that.

We implemented JIRA six months ago.

The stability is good. We have around ten users as a start. 

Impressive

We have contacted technical support. Their response was prompt. 

The initial setup is not that difficult, but it's not that simple either. That is why it took us  about three to six months to get it up and finalized.

Via our in-house.

Right now the price is fair but once they move to the cloud, that model may not be attractive anymore.

It is an excellent tool to summarize and get our stacks of data into a platform for operational overview and interface tracking. It is very useful for us. 

I would rate JIRA a nine out of ten. Not a ten because of the GUI pie chart. The beauty of the dashboard is not perfect, so I subtracted some points.

Our primary use case is ALM, which is very well supported by Atlassian.

We have realized an improvement of 30% in terms of the duration of our small projects (six months with three to four people).

The most valuable feature is the full integration between Work management, Source code management, and Test Automation.

This integration allows a full traceability during the development processes, which is mandatory for some industries like automotive, or security

The hierarchy for Jira tickets is too flat.

We use it mainly for Scrum management.

Most of the projects which we have taken in were using a waterfall model, which is very hard to convert into an agile or Scrum model. It helped our customers have visibility into requirements and reporting, since they were mostly using spreadsheets. We could help give them a clear cut view of what was happening on ground with development and the test database.

Reporting: It gives a nice report of my backlog and what my team has currently spent its efforts on.

JIRA still has their own backtracking tools. It should have a better visibility into HPE UFT. Most people use functional testing tools, like QTP. They need to improve their integration to make it seamless. 

You can do a lot with the tool but again, but it is not a 100 percent solution for everything. We have a lot of acceptance criteria coming through it, but JIRA doesn't support it. Therefore, we have go to different user stories and break them down. 

Using a cloud instance, it is always stable for us. It is not a problem at all.

We use a cloud instance for most engagement, so scalability has not been an issue.

My company has a 100,000 people, so we always can find someone within our organization who can help fix an issue.

I was not involved in the initial setup.

I understand JIRA is quite expensive.

Most important criteria when selecting a vendor:

1. Usability: It should be easy to use. People should not have to undergo a lot of training because it should be intuitive.
2. It should be scalable and a cloud solution. 
3. It should not be expensive. Cost is a major driver because I work in pre-sales.
   

We are using it for software development tracking, bug tracking, feature tracking, and so on. 

We are using the cloud version from Atlassian, and we have its latest version.

The way we can define and customize the search queries for the tickets in Jira is most valuable.

The way to configure it can definitely be improved. It is very difficult and complex to configure. Its configuration should be simplified.

I don't have any requirements for new features. It is a standard system, and we use just a part of the functionality.

I have been using this solution for five to ten years. I use it on a daily basis.

Its stability is good. In the last five years, I haven't seen any outages. 

We are a very small team, and we don't have any requirements for scalability.

I have not contacted their technical support.

The initial setup and the out-of-box features and functions are very straightforward. I would rate it a five out of five in terms of ease. You can just create an account and start to use it. 

It is a cloud solution offered by Atlassian. There is no on-premises setup, and it doesn't require any maintenance from our side.

It is subscription-based, and we probably pay yearly. I would rate it a four out of five in terms of price.

I would rate Jira an eight out of ten.

My primary use case is using the boards in working stories for freeing up the backlog and assigning tasks to my developer team. 

No other stats of graphics or reports from Jira are used. We use Grafana instead of that.

I really enjoy the easy way I can follow up the story's progress even when they are in progress or we test bug stories. When issues arise, they can play back to the team in order to fix all the bugs. They have a view of the backlogs in the current sprint and the next sprint. 

The initial setup is straightforward. 

There are many Jira add-ons available, however, we aren't using those yet.

The solution is stable.

We've found the scalability to be good.

I alternate Jira with Excel. I manage the progress of the stories in an Excel chart with dates on work progress or thing to do. I don't like the progress or the stage changing from the stories in Jira.

I've been using Jira for about four years. It's been a while. 

The stability is quite good. There are only some updates that are made by IT, however, it's working fine for me. I haven't dealt with bugs or glitches. it doesn't crash or freeze. 

The solution is scalable. I've tried other solutions, and this one seems to be the most adequate for my needs.

We have about 1,000 users worldwide. There are several projects running in several parts of the world. 

We do not plan to increase usage. We are using it as we need it and no more than that.

We've never faced any big issues and we have never had Jira go down. Therefore, we've never had a need to contact technical support. I can't speak to how helpful or responsive they are.

I found the initial setup to be pretty simple and straightforward. It was not an overly complex process. 

However, largely, we are just testing Jira. I can't speak to how long the deployment takes. 

I have three teams that can handle deployment tasks. There are six people in one, seven in another, and ten in the third one.

We do not use resellers or integrators to assist with the initial setup. We can handle the process ourselves.

I don't have any information in regards to the licensing or cost of the solution. It's not an aspect of Jira I handle. 

I have tried or tested other options such as Excel, Monday, Trello, Tetra. In comparison, for how I use it, Jira is the most adequate for my daily job.

We're a customer and an end-user.

Nowadays I'm using the web version of Jira for my client. I'm managing my boards, my sprints, and my backlog which are all working on Jira except the retrospectives. These are made in a code and not written down in Jira.

I would recommend the solution to others. It's easy to learn, easy to handle, and we've never experienced any downtime for a year and a half at least.

I would rate the solution at a nine out of ten. I haven't fully utilized the entire product, however, from what I have seen, it's exactly what we require. 

My primary use case of Jira is as our project management tool for monitoring and planning.

The most valuable features are the speed and especially the search capability - I don't think any other platform can compete on those.

The main area for improvement is the high cost of the product.

I've been working with Jira for two years.

There are some small issues with stability, like unexpected updates, but overall it's good.

I think you can scale Jira as far or as big as you want, it's very scalable.

Jira's technical support is easy to communicate with, and they are very responsive.

This product's cost is much higher compared to other platforms, but it's worth the extra cost. Some add-ons are only available at additional cost.

Jira is easier to configure than other platforms like DevOps. It's fairly easy to learn so long as you dedicate some time to it and is easier to use than other solutions. I would rate this solution as nine out of ten.

We use Jira for project management for the development teams. Additionally, we do backtracking and managing the backlog but it is more of a development team tool.

There are a lot of plugins in Jira and we purchase the ones we need.

Jira can improve by making user management better. It is not easy to have visibility of who has the right to do what. Only the administrator has this visibility but there should be the option for other users too.

I have used Jira for approximately 10 years.

We have never had an issue with the stability of the solution.

We have approximately 400 people using the solution in my organization.

The support from Jira is good.

The configuration can be complicated, there are a lot of options.

We have a technical team that does the implementation and maintenance of the solutuon.

The basic price of Jira is reasonable, but for each plugin, we have to keep paying more. When you add it all up, it can be expensive. The main problem we face is we are forced to purchases plugin licenses for users who are not going to use them. For example, we have Jira licenses for approximately 450 people but if we only want a purchase a plugin for few people it is mandatory to buy the license for the 450 people who have Jira licensees. This is a problem because sometimes we need plugins for the product manager or for people in charge of the report, not everyone. For us, it can be very expensive in the end, they should alter this policy to allow plugins for only a set number of licenses.

My advice to those wanting to implement Jira is to have a lot of support. In our company, we started out small with only approximately 25 people and then we expanded quickly. Jira can be complex to manage, and it is better to have some advice or some people to help with the implementation.

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.