Jira Reviews

JIRA: Product is well liked but we have had performance issues. Premier Support: Knowledge is very good and they are willing to bring in other people when they need to. The Premier Support team was very thorough and very responsive.

I think that if you look at how we troubleshoot, Premier Support has allowed us to not waste our time with dead ends, to have better focus, and get to root case much faster. Even though we still have monitoring in place, for root cause analysis we rely heavily on Premier Support and don’t waste as much time.

For our Premier Support, We would like to have on the call interaction all the time. The session we’ve had recently has been valuable, but we would like to see more live sessions/interactions.

Purchased Sept. 27th 2014.

Our Premier Support engineer was extremely helpful with deployment. I was pleasantly surprised, the engineer gave us guidance, looked for any potential issues, and was above and beyond in terms of service. They did a really fantastic job.

From the beginning that has been the main thing we have been working on and thru Premier Support, they have done a good job working on our side, and escalating to a larger team when needed.

The Premier Support team was very thorough and very responsive.

The Premier Support team was very thorough and very responsive.

We previously used the standard Atlassian support and then jumped from standard to premier. In terms of tracking, we had other defect tracking, but now JIRA has been a replacement – it is the tool of the future.

The initial setup was straightforward.

Yes, we have other vendors and tools – evaluation is ongoing.

I would tell people to understand your growth and usage up front – really comes down to understanding that and keeping it under control. We grew too fast and weren’t prepared for the issues that came with that; you want to make sure you have a good performance testing environment in place, datacenter etc. so you’re not scrambling afterwards.

I use the tool to review code quality and communicate with the QA team. I also use the product to raise tickets with my senior management for issues I cannot resolve.

The user interface is simple. It performs well. It is easy to use. Anyone can use the product.

The stability could be improved.

I have been using the solution for one year and two months.

I haven’t had any issues with the stability of the tool. I rate the stability eight out of ten.

The initial setup is simple. We have completely migrated to the AWS cloud.

I will recommend the tool to others. Overall, I rate the solution an eight out of ten.

The design of the interface is clean and not too busy visually.

I'm really new to Jira and I haven't used all of the features. However, it is quite difficult to use and manipulate. It was a little complicated for me and I don't know if it's difficult globally for others, but I had a difficult time understanding it at first. I used it for issues,  epics, stories, tasks, and sub-tasks. For first-time users, Jira could be made better to help them understand.

When you want to create something in Jira, whether it's a story or an epic on a task, you have to create a thing called an issue, and inside the issue, you have to put what type of issue it is. Either it's an epic or a story. The fact that it's called an "issue" was a little confusing for me because I didn't know where to search when I wanted to look for tasks and stories. I didn't know that I needed to search for issues and not only tasks or topics.  

I have been using Jira for approximately one month.

Jira has been a stable solution.

I have found Jira to be scalable.

We have 20 people in my company using Jira.

The setup of Jira was simple.

I did not compare Jira to other solutions.

I have not had a lot of time to explore the solution. My rating might be higher if I had used it more.

I rate Jira a three out of five.

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.

We use Jira to create releases, tasks, sprints, and collaborate within teams. The solution can be deployed on both the cloud or on-premise.

Jira has a useful user interface and overall is easy to understand and learn.

Performance is something that can always be improved upon in a feature release. Additionally, it would be a benefit to add Markdown in Jira because sometimes it might be better to describe everything in Markdown because it is a common language structure.

I have been using Jira for approximately eight years.

Jira's stability could improve. We have experienced times when we were out of memory which is possible due to a memory leak. It is hard to pinpoint the cause, it could be the operating system.

I have had to contact the support when I had some questions about the upgrading process and they answered in a timely manner.

I have previously used a comparable solution to Jira and the largest benefit was it was free.

The setup is not difficult. I have done it a few times in Kubernetes and did upgrades, the experience was straightforward.

There are other solutions that are free making this solution seem expensive in comparison.

I have found the cloud deployment better than the on-premise. However, for those wanting to implement this solution, I would advise them to compare the pros and cons of each before making their selection.

I rate Jira a ten out of ten.

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.