Jira Reviews

I'm from a QA background and we used to do automation. It was far easier to link JIRA with our QA automation frameworks because JIRA has a lot of public APIs that we could use. Also, the burndown charts and the ability to manage different frameworks of the adjoint model are helpful. We could use scrum in one project or Kanban. So it was easy to manage the transition from one framework to another. Those are the things I found useful, but I haven't seen the case of TFS yet.

JIRA could simplify the query mechanism. Running a query for tasks, stories, and so on is far easier in TFS. The algorithm is easier. In JIRA, it's a bit complex in terms of what advanced search queries we use. Sharing them is also a problem. Because TFS is on the cloud, we can easily save that query and share it with our team members. So that is one area where JIRA has some room for improvement.

JIRA is pretty much stable.

JIRA is far more scalable in terms of using different frameworks, burndown charts, dashboards, etc. The size of your company doesn't matter. JIRA has the capability to work for smaller organizations and larger ones as well.

JIRA's technical support is absolutely fantabulous. I had used it in the past when I was working at my previous organization. And when we wanted to link it with a framework, they helped us out with the API we were looking for. There were certain areas where we were looking for a specific API. And also they have a lot of options in terms of packages that you can choose according to your company's needs. They had custom packages available. You do not have to buy a larger package. They have smaller packages for smaller organizations. So that's something exciting.

JIRA is fairly easy to set up. That is not a problem.

JIRA's pricing is very economical. I would say that JIRA is a great deal more economical than Microsoft. So pricing-wise, JIRA is also good.

I would rate JIRA nine out of 10. From a technical background, it depends on what you would like to use — which stack you want to go for. In other words, it depends upon the kind of infrastructure you have right now. For example, say you are developing software on Microsoft's .Net framework, then you are obviously already using Visual Studio and Microsoft Stack. In that case, it's a lot easier to integrate with TFS. But if you are using open-source solutions, like a Java platform, you can go for JIRA. So it totally depends upon the technical capability, or technical infrastructure one has.

It is helpful for bug tracking in software development. If developers are doing some work and testers notice some defects, they can flag it in JIRA. For example, I track my day-to-day work in JIRA so that others know what I'm working on. They can look at JIRA and don't need to contact me. From JIRA, they can find out that I am working on this project and spent two days on it, etc. It's used for so many things, like task management, bug tracking, and release management. 

JIRA is not for deployment. For deployment, you are going to use some tools like Jenkins. It's meant for all the features that are going into that deployment. 

Different teams within the company use JIRA. For example, everybody in the engineering section uses it, so altogether, that's around 200 people.

JIRA gives us a lot of visibility. For example, if you're planning to release a given feature, you can track the status of that feature. Is it working correctly, or does it have some bugs? So you have a high level of visibility on the work. 

The JIRA user interface looks great. It's an overall good experience. It's very intuitive in the sense that you understand how it's going to work. It's very self-explanatory, and it's beneficial overall. Each release has different steps and phases, and the whole thing can mostly be captured on JIRA. The workflows are really helpful. 

So at one point in time, they did a huge UI upgrade. At that time, I felt like they had changed something, so it was hard to figure out. Now that we are habituated, it's not an issue now. We had gotten used to the old interface, so things changed, we felt an initial discomfort. That's the only thing. Otherwise, there is nothing I dislike about JIRA.

I've used JIRA since the beginning of my career and nothing else.

I haven't had any issues with JIRA's stability so far.

The scalability of JIRA has always been good. The response time is always fast. I've never had any issues with scalability. I think no matter how much our usage increases, we'll continue to use JIRA.  But, I think our usage is at an optimal level. 

From our end, setup is basically book-keeping. I can't say much about the overall setup because there is an administrator for JIRA who adds users and sets everything up. I haven't been an administrator. I'm just consuming the JIRA. 

Initially, I think administrators are going to set some things like configuring the workflow should and then how you want to say things. But other than that, if you set it up once, it's going to work. You don't have to do much maintenance.

I rate JIRA nine out of 10. I would recommend it.

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.

We are using it for project management.

It helps everyone to be on the same page.

Its integration with Bitbucket, Confluence, and other related products that Atlassian owns is most valuable.

If CI/CD is integrated with it, it would be better. I've used Azure DevOps before, and it's nice to have everything, such as CI/CD Repos and other things, integrated. Jira has fewer integrations. Azure DevOps has an easier interface, and it has got everything in one spot. I don't have to jump around in different applications.

It should have more Trello-like features. There are some things you can do in Trello, but you can't do them in Jira, which doesn't make any sense because Jira bought Trello.

It looks pretty solid.

It looks scalable. I haven't seen any issues.

It is being used extensively at the moment in our organization. Currently, IT departments are using it.

I have not interacted with them.

I wasn't around during the setup.

It has a lot going on. They own Bamboo, but right now, we're using Jenkins. 

I have used Azure DevOps at another company. I would advise going for Azure DevOps because it has everything. You've got your DevOps, and you have your Repos. Everything is integrated.

I would rate Jira a six out of 10.

Our primary use case of Jira is for tracking corporates and for new test cases where we need to execute monthly releases. We use it for test management purposes, whether for tracking or test use cases in their different cycles. We log everything on Jira and are very dependent on it. We are customers of Jira and I'm senior quality assurance person.

We've seen a benefit from the tracking of the release sizes and their status, it's very clear and simple, and the UI for Jira is easy to understand. 

Jira has a good dashboard. If I'm running an automated test script on different levels, say API automated or UI automated, and want to track automation status in the dashboard, I can get the overall status. I know how many cases are automated with the API or the UI and how many cannot be automated. It's a good feature. 

Jira could be more user friendly. When I started using it, I faced difficulties in different project selections and there were issues with bugs. It was not straightforward. I feel it could offer an improved user experience. I have a small issue that whenever I log out there's a bug and for a fraction of a second, I'll get a notification that then disappears before I can do anything about it. 

I've been using Jira for quite some time. 

From a performance perspective, I have faced many issues, some bugs and glitches, and there has been some down time. In general, it's a stable solution. 

The solution is scalable; we have BA, QA and Dev Ops people all using Jira. Everyone has  access, but certain users have access to certain areas. It's our test management tool so we use it a lot, everything is tracked on Jira and our reports come from there. 

We haven't used the technical support.

I used TFS before Jira. They are similar tools but I found TFS to be a more complicated solution.

The deployment took a few hours, some aspects were more complicated than others. 

I'm not involved in the licensing aspect. 

I rate Jira seven out of 10. 

I am working on a project which involves moving Jira onto the Azure boards. We use Azure DevOps for our repository and pipelines and we are looking to move on to Azure boards from JIRA for our ticketing or change request management.

Jira has helped our company because the board layouts are easier to use and has helped us see what is happening in regards to stories and bugs.

The layout, workflow, automation, and metrics are helpful in Jira.

The flexibility of defining your columns that can possibly contain multiple statuses is important. When you have teams that are different levels of granularity, the C levels, only care that it is in progress, but the leads want to know that it is in QA or development. You can accomplish these types of things with JIRA.

The biggest complaint industry-wide about JIRA is they need to purchase additional extensions, such as reporting automation. If they could provide some additional extensions from the initial purchase it would be a huge benefit.

When using the service desk and the developer, the transition could be better between the two. For example, we asked the support desk to send a ticket over to the development and it was a little bit cumbersome. We had to recreate another ticket for development, then we had two tickets, one service desk, and one development. It would be beneficial if the process was more smooth between those two packages.

I have been using Jira for approximately eight years.

The stability of the cloud version of JIRA is very good. However, we did have some issues with the on-premise version but the issue could have been because our servers were overloaded.

The scalability has been very good.

We have approximately 40 people using this solution in my organization, which is mostly everyone. It is used by many departments, such as project offices, development, and coding QA. The only department that is not involved in the use of the solution is the company support. I had worked at a company previously that used the JIRA service desk for their support and it worked well.

I have previously used DevOps and Rally.

JIRA installation is complicated. It is similar to a lot of other systems, the more flexible they tend to be more complicated they become.

We do the maintenance of the solution which is adding users and moving them around. The solution is very hands-off, it does not require a lot of maintenance.

We currently are evaluating other options and are doing a study to see if we are going to continue using JIRA or move to something else.

I would advise those wanting to implement this solution to contact an expert. 

This solution is a top-of-the-line CRM, I have used the others solutions, and it has the most flexibility and the best visibility.

I rate Jira a nine out of ten.

We use Jira for enterprise planning.

We like team collaboration and cross-functional collaboration.

The history with Jira is that it is a bit complex for many users.

There are too many features.

The user interface is complex.

I have been working with Jira for five years.

We are migrating to the latest version.

Jira is pretty stable.

It is scalable enough.

We have 1,000 users in our organization who are using Jira.

We plan to increase our usage.

Before Jira, we did not use any other solutions.

The initial setup is straightforward, nothing out of the norm.

We had a perpetual license but have changed to a subscription.

We are not satisfied with the pricing. It has become more expensive.

We would prefer it to be cheaper.

We evaluated other solutions before choosing Jira. We chose Jira because it is widely used.

I would rate Jira an eight out of ten.

I primarily use the solution for project management. 

The product is quite easy to use and simple to navigate.

The solution isn't too difficult to learn.

It's flexible and it can provide a lot of different options, such as dashboards, that you can create and manage. You can really tailor-make your own dashboard depending on your needs.  

It's quick and very stable. 

I don't see many issues while I'm using it.

You can basically communicate with all kinds of different teams that are using Jira and you can do that under the product, as a single platform.

Sometimes the solution doesn't communicate well with other platforms. It's quite difficult to integrate things and make the data flow from A to B, to Jira, and then back to other areas.

Nowadays, you see a lot of product management tools, like monday.com and they are very user-friendly. They offer features that allow for cosmetic changes, and you can actually change the color and the form to your own liking. ira is lacking some of that flexibility. It's not critical, however, for the wider user base, many would like to see that.

I've been using the solution for three years. It's been a while. 

Overall, the performance of the tool is quite reliable with few bugs or glitches, and it runs very fast in the browser It doesn't crash or freeze.

The solution can handle a lot of tickets. I've seen it handle more than 10,000 with no problem. It's almost unlimited in terms of scalability.

I'm a customer and an end-user.

I'm using the latest version of the solution right now. I cannot speak to the exact version number we are on currently.

I'd rate the solution at a nine out of ten. We've been very happy with its capabilities. 

I would recommend the solution, as it is quite powerful.