Jira Reviews

We use Jira for ETCM. It's for ticketing with QRadar.

We integrate Jira with QRadar which is helpful.

The performance is quite good.

It has real-time collaboration. 

It provides good visual data easily.

While Jira integrates well with QRadar, it is not integrated with Splunk for example.

I would like to see more integration available with more tools.

Jira is not used in my company; in fact, it is not used at all. Jira is a project management tool that I use at school and during my internship.

Jira is stable. I have not experienced any issues with the stability of Jira.

We have not had any issues with the scalability of Jira.

They provide technical assistance. Whenever you need something technical, they are quick to respond.

The price seems reasonable to me. It's very similar to Splunk. 

I don't believe it is expensive. 

I'm not sure if they provide a free version, but we need free versions of everything to try before we buy. 

I believe we simply require a longer, free version.

The initial setup is simple. I didn't do it myself, but I've read the support, the guide, and it appears to be simple.

I did some research for a school project. I needed to compare it to Splunk and a few other tools. As a result, I'm not particularly interested in purchasing them.

I don't use Jira very often, and I don't have a lot of experience with it.

I would rate Jira a seven out of ten.

I use Jira for user stories, tasks, bugs, track releases, track backlogs issues, burndown, and test reports.

Jira has helped our company because it is easy to track releases and deployments. It is easy to track which tickets have been done or are still pending and left to be completed.

Jira's most valuable features are ease of use, simple to understand, and highly flexible. Additionally, you can use kanban or scrum which is a benefit.

The reports in Jira can be improved, especially for test reports. I find it difficult to customize and integrate for different testing purposes.

The out-of-the-box version of Jira has minimal to no testing functionality. I have to use Zephyr to be able to track testing. The time logging is also not easy to use, or user-friendly.

In the next release of Jira, there should be test cases in the test reports. Better burndown and burnup reports should be enhanced. Additionally, the usability of time logging could be better.

I have been using Jira for seven years.

Jira is stable and reliable, we have not had an issue.

I have found Jira scalable.

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

I use the solution extensively in my organization, I use it daily.

I have not contacted support from Jira.

When I came to this company I had already used Jira. Previously, I was using quality control from Quality Center and Azure DevOps.

The initial setup was straightforward overall. The process takes only 10 to 15 minutes. However, the setup could improve.

We did the implementation of the solution in-house.

We have two administrators that do the patching and maintenance of the solution.

I would recommend Jira to others.

I would advise others to be sure to do the reports correctly because there can be some challenges in reporting and in the testing phase.

I rate Jira an eight out of ten.

We use Jira as a help desk, an IDSM. We use it on a daily basis. Every ticket gets opened on it.

It's very simple to change the workflow and adapt it. Jira is very user friendly for the agent and the user.

It's a very customizable solution, but as a customer, we're always looking for additional customization. There could be better customization in future releases. If we changed from Atlassian to another product, we would look for a customizable solution.

I have been using this solution for many years.

The stability of Jira is good. We haven't had any issues with stability or performance.

It's a license-based software, so if you pay more for the license, the solution becomes more scalable.

Customer support is usually good. I have had no issues with them. 

Setup was straightforward. There is no dedicated team for maintenance. Our IT department handles that. It's a simple solution.

There are no additional costs to the standard licensing.

I would rate this solution 10 out of 10. I recommend Jira. For the time being, everything is good. Their support is good. The platform is good. There are no issues with them on any level. We mainly picked Jira because of its stability, integration, and price. If a solution is well integrated in our environment, and it's not costly, why not configure it?

The biggest thing I have taken away from working with Jira is that it's very simple.

We use Jira in our organization for lifecycle management.

The solution has helped our organization do lifecycle management easily.

I have found the most valuable features of Jira to be ticketing, life cycle workflow, definition, and creation. Many of the features are useful.

The solution could improve by having its own tool for quality lifecycle management.

I have used Jira for approximately nine years.

The stability of Jira is good.

Jira has good scalability.

We are using this solution extensively. We have more than 5,000 using the solution in my organization.

We have been satisfied with the technical support from Jira.

We have used in-house developed tools previously and we had to do a lot of customization and this is why we moved to Jira.

I would recommend this solution to others, it is a good option.

I rate Jira an eight out of ten.

We use this solution to manage our projects.

Jira is a great software. There is not much to complain about, other than it doesn't fit very well into our current Microsoft environment.

Jira as a structure has Confluence for documentation, and for what it is offering it is a strong suit with Atlassian.

The only thing in our current setup that is a bit difficult is that Jira is a bit of a black box. Only we see it, our customers do not. I know that we can change it but we have not done the work to do it.

Jira is not compatible with our current Microsoft infrastructure. 

We are using SharePoint along with WorkPoint in our environment, which is used for document management and process management. For projects, it is a better connection between HelpDesk and the projects. Moving into SharePoint would help.

If Jira would be interested in offering a SharePoint version, it would be beneficial.

I have been working with Jira for approximately five years.

Jira is a stable product.

We have approximately 50 users in our company who use Jira.

I am satisfied with the technical support of Jira. It's fine.

I have tested Plumsail Helpdesk. There's only one thing that worries me. Due to GDPR, we cannot use email yet in Plumsail. That is the only thing, use email to create tickets.

I don't know where the mailbox is in Plumsail, otherwise, it just ends up in us using SharePoint. It looks very promising.

It is very affordable at the entry-level. When you get larger, the pricing becomes very, very steep. It is the same for many other solutions, but I find it expensive when you get larger.

We are currently using Jira but want to move the help desk to SharePoint. 

We have a Microsoft environment. SharePoint HelpDesk would fit better into our environment. As we are larger than we originally started, we have to make some changes to our current setup.

I also find Plumsail HelpDesk quite interesting.

I don't know what to compare it to. It is not an A product, but it's a strong piece.

I would rate Jira an eight out of ten.

We use Jira for our in-house projects. We use Jira Cloud and Bitbucket. We are not actively using Confluence.

We are a small company. We can manage our project tasks with other tools, but I prefer to use Jira on the cloud because people forget what they have done, and we need to see who did which task and when.

We love the bulk edit feature. Jira also integrates well with Bitbucket. 

Workflows can be improved. We don't use workflows because we can't handle that much complexity. Its interface could be more intuitive for workflows.

I have been using this solution for three years.

It is very stable. I have been using this solution for three years, and I never had to contact their support.

It is scalable. We have six people who use Jira at the moment, and they don't have any issues related to slow response. Everything is fine for now.

I never had to contact their support.

In this company, I have only used Jira. In earlier companies, I have used other tools such as Microsoft Project, Redmine, and Service Bus. 

It is easy to set up. We can use project templates. We can use classic projects templates or create new templates. Classic is enough for us. Our management doesn't want reports from us. We use templates for our daily progress.

Its price is good and similar to other products. It is about five or six dollars per user.

I got it set up when I joined this company, and now I manage users here. It has integration with Bitbucket. It is fine for us.

I would rate Jira a nine out of 10.

We use this solution for project management.

It can be used across a team. Managers can assign tasks and then they can track the progress. They can put the start dates, end dates, and everyday comments.

They can upload the relevant files to that module.

Jira is used to manage a sprint, which is the terminology used in the agile practice of project management. Sprints can be tracked fully using the Jira software. A sprint is typically a part or a subset of the entire work. It has a definite goal.

For example, if I am building test software, and building the login page is one module, then I can track the work created from the starting stage to the end.

It's a part of an entire software application. If a login page of a website is a subset of an entire website, I can track that right from when it started, how long it takes, what is pending, and how long the control test is.

Basically, you can clump it all together as if it is a team and you can measure the speed of the team. It enables the predictability of a project and helps determine when it can go live.

All of the tracking features are the most valuable because it allows me to see where we stand today and every day. 

At the end of the day, I look to see what is pending, what is as per my expectation or as per the speed, and what is not going.

I can put in my comments or give a direction, or tag any other person if they need any help if they are stuck.

The user interface could be much better, although it's good enough to do the job.

I don't see the mobile application for this particular application. I use it on PC. I tried to download the application, but there are some constraints to using it. It doesn't link properly, it doesn't detect my Jira board, even when I have entered the name. I don't know how to use that app. I download and tried, but there is confusion. There is no clarity on how I can map my desktop account with the mobile application. There is definitely room there to improve. 

There should be a way to integrate the mobile application or in some way, make it more clear because at first instance, I didn't understand how to use it.

We have used Jira over the last seven months.

It's a stable solution.

We have a team of eight members who are using Jira. They are divided into teams with each team using different boards. 

For example, one team is managers who are using it, whereas another is a team of developers using a different board that can be created and used for their purposes.

I have not been in a situation where I have needed technical support. Everything has gone well.

The installation is typically done by my IT team. I don't have exposure to that.

Prior to Jira, we were evaluating Microsoft tools, but I don't recall the name. Possibly Microsoft Task.

We were evaluating Microsoft products for the same purpose.

The decision is a collective team decision. It may have been that Jira is easier to implement across the company.

It is a well-crafted product. I don't have any concerns.

I would rate Jira an eight out of ten.

We are using Jira to manage our development sprints.

The most valuable feature is working with sprints and having the ability to create sprints. You can create and move onto the next one.

Also, for example, while I don't use a lot of plugins, when you have a ticket then all of the information you can put into it is centralized.

There are so many opportunities that you can create almost anything.

The sprint-related graphics need to be improved.

They are using story points for the sprint breakdown graphics. When you have five large stories with several story points, in the first week of the sprint, nothing gets done. This means that you have a flat line and then, in the end, all of the stories are done at the same time. So, we created all of the graphics but they were useless because it was just a horizontal line and then at the end of the sprint it dropped down to zero points. Basically, it was a square.

In the next release, I would like to see a good graph that takes into count what you put into your stories.

I have worked with Jira, on and off for four or five years. I last used it in April, a few months ago. I have always been working with the latest versions.

It's a stable solution.

Jira is scalable, but you will need knowledge of every team because in every organization you have several teams that work differently.

You need to understand and know how to scale and be prepared.

It doesn't require many people to maintain Jira. 

You can configure a lot yourself, depending on how many rights you get in the application.

If you have enough rights, you will have a lot of opportunities to configure it in the way you like.

I would recommend this solution to others who are interested in using Jira because you can do a lot with it. However, I think that as you start working, you should start small. Work with it and try to configure things that you really need. 

Involve the whole team in what you are going to use and how you're going to use it.

I would rate Jira an eight out of ten.