Jira Reviews

I work for an insurance company that has developers who need to be tracked. We're working on converting the spreadsheet into a Kanban flow environment. I'm the program manager/master. 

The solution is very powerful, has many good features, in particular a good reporting capability. I like many of the features, and I have the benefit of having a very skilled Jira administrator helping me out because I'm a PM. 

The solution is not as intuitive as it should be and you have to play around with the environment quite a bit before you get a handle on how things work. One of the issues is that it's usual for a ticket to have a primary developer on it and other people supporting, but that's not possible in Jira. They have a very thick policy and a ticket can only have one assigning, although it may be possible to do it as a number coding, I'm not sure. I'd like to see the solution include a feature whereby you can link stories visually, to explicitly show the connection between a user story and a task. 

I've been using Jira for several years. 

Scalability of the solution seems fine.

Technical support could be improved. When you submit a ticket, it can take two or three rounds before you get what you're looking for. I send the ticket and receive an irrelevant response, which doesn't help. You can go backwards and forwards with them and never get there which is very frustrating. I'm not sure if the user community is that helpful. I've submitted two questions but haven't yet received a response. 

The initial setup was quite complex. 

The solution is fairly good at doing a lot of things, and is potentially very good, but it takes some getting up to speed on. I've used a product called Kanban Flow, and that's very intuitive, very easy to use. Jira seems to be more complicated and requires having specialists on board so that if you have a problem, you can get help immediately without having to go through the ordeal of submitting a ticket and waiting two or three days to get a response, which may not be helpful at all. 

I rate this solution a five out of 10. 

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.

We are mainly using it for project management and issue tracking. It is used by development, QA, and IT operations. It really goes through the whole gamut of project management.

We are not using its latest version. We are usually a little bit behind on versions.

Jira is a pretty capable product, and a lot of features are valuable. We value being able to set up separate projects and configure teams in them, set up sprints, and manage our sprints with its history tracking. These are all very useful features. It has been a very popular product for our work.

Because I am a developer, I would like integration with Git Source Code Management so that for tickets, we can reference the code where the change has happened and where the issue is. This feature might be there, and I probably haven't discovered it.

I have been using this solution for probably six years.

Its stability has been very good. Every once in a while, we have a problem, and the service stops working. I don't think we have a very robust installation of it, but if there is an issue, it is back online very quickly.

Most of the issues are probably related to the server needing patching or something else. It may not be running on the appropriate size hardware. I know it is not a well-funded product at our office.

It is impressive. We have all our projects on it, and we haven't really had reports of any issues. We haven't yet stretched it to its limitations, but it has managed to meet our requirements, even in this minimal deployment. I am pretty impressed. 

I didn't directly contact them, but I am sure at some point we have. We usually have a contact person, and we pay for the full support.

We are adopting multiple products, such as ServiceNow, but they do different things and are for different purposes. There is a talk about replacing Jira with ServiceNow, and we're not too happy with it because we all liked Jira, but sometimes this kind of stuff happens. ServiceNow does have crossover features, but it gets into problems for us when changing from one system to another.

I didn't set it up, but I haven't heard of any issues with the implementation of it. It seems to be very straightforward.

I would recommend this product. Overall, it is a good product. It supports scrum and agile developments. It has a lot of benefits that can be applied very quickly in organizations.

I would advise others to do a test installation and make sure that it fits their needs. Experiment with the multitudes of features that it has. I know there are lots of modules. There are probably many features that we are not using. 

I would give it very high marks. I would rate Jira a nine out of ten. There is always something you could improve on it.

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.