Jira Reviews

We are using Jira Interview to handle all the facts from clients and schedule calls with them. We have a different operations department that configures Jira, and we have technical people that help us choose the deployment model. 

The main reason we are using Jira at this time is for a different dashboard and chart. The major one that we are using is for the stock analysis, and it's nice to get that time log for our team, get the score of the game, 40 points delivered in a week or a month. we are using Jira for following purposes:

Issue tracking
Customizable workflows
Estimation & work logging
Progress reporting
Scrum boards
Kanban boards
Project-level permissions
Project backlogs
Email notifications
Roadmaps

Productivity increased by using this tool and organization can measure the productivity of a resource. early alert being displayed in the case of project failure and success. Org can identified the work load on resources for a day. 

We like the test cases in Jira. The orange dash items view was great, and we like the features and layout of the data. It's quite different, and people are now getting their items so quickly. We love the bulk edit feature. Jira also integrates well with Bitbucket.

Sometimes it takes time to load the data.

I've been using Jira since 2015.

Performance-wise, Jira is good, but sometimes it takes time to load that data. 

Jira is scalable. We have about 470 people working with Jira in our company.

The support team is very helpful and supportive. I requested multiple things and faced some concerns, they were very cooperative and responsive.

Asana. Jira has better work flow and features relative smart and easy to use.

It is easy to set up. We can use project templates. We can use classic projects templates or create new templates. We have also build the custom workflows for the custom templates.  We use templates for our daily progress.

I would tell potential users that they should all get it.

On a scale from one to ten, I would give Jira an eight.

I'm head of the IT service desk, and we're using it to track IT tickets from the users. If there is an incident or someone requests information or services, we handle all these requests through Jira Service Desk.

Jira is flexible and accessible for the end-user. It lets users track their requests. The look and feel are good for our purposes. I'm the IT service manager, so I'm like the director. A cleaner interface helps my team stay on top of the service requests. We used to just take requests via email, and we had some kind of old IT tool, but it wasn't as effective as Jira. And because we are connected to Power BI, we have better visibility. You have a range of metrics so you get some good insight when you integrate Jira to Power BI.

My colleagues started dealing with Jira in 2019, and they're still using it. And my team implemented the Jira Service Desk in 2020 because the rest of the company was using Jira.

Stable. What about scalability? Is it scalable?

We get outstanding technical support through our partner Valiantys, which is a French Jira distributor certified by Atlassian to resale Jira.

It's not a complex implementation, but it's not easy either. I think it's somewhere in the middle. It's an average software implementation.

Jira is raising their prices for the license, which is like a trap because many other providers offer services like Jira but for much cheaper. And now they are making us move to the cloud. They gave us a deadline to migrate from the on-premise Jira Service Desk to the cloud. It's been two years since we started using it, so I think we will get a discount.

I rate Jira Service Desk seven out of 10

We are using primarily using Jira for the project and issue tracking mostly.

One of the most valuable features is querying because the jQuery function is very good. Additionally, we can create good designs very easily.

There are too many restrictions in Jira. In DevOps, you can access the dashboards easily, but in Jira, you should have more administration rights. In our organization, there are some restrictions on creating dashboards and other features. Everything should be accessible with all access rights for everyone.

Jira should allow you to create and develop pipelines easily. In India, we have to purchase them separately or integrate other data tools. All these tools should be in Jira.

I have used Jira for approximately 12 years.

Jira is stable.

In my experience Jira is scalable.

The technical support has been satisfactory but could be better.

I have used DevOps and the main difference between DevOps and Jira is the test cases. You can have test cases in DevOps, but not in Jira. This is what I have observed in my recent comparison. Jira has jQuery and it is far better than what they have in DevOps. There are some filtration and grouping settings in DevOps which I do not like.

The initial setup is easy.

Jira is expensive and a lot of people are choosing DevOps because they are cheaper, open-source, easy to use, and have basic licenses. Jira should decrease its price to be more competitive.

I rate Jira an eight out of ten.

Similar to the whole solution stack, we use Jira for security and for operational data storage. We also use it for custom-made API structures, moving data from the cloud to legacy on-prem infrastructures so we can use it to develop failing interfaces. We're customers of Jira and we license the solution. Our company has a form of strategic alliance where we buy the product, pay the fees and use the solution. I'm a senior technical project manager.

The benefit of Jira to our company is that the product is extensible. We can integrate other tools and different interfaces into it. You can look at what's being done, how it's being done and know how to improve it. That includes things like optimizing performance or scanning the structures we build for security vulnerabilities. Extensibility is the most effective way we can create products and services for our clients.

The value of this product is that it offers a common language set so we can bring people into projects and get them up and running almost immediately. We know the language. It's the training and education content that's key and there's enough out there, whether it's paid training or free training, that gets people up to speed pretty quickly. Following on from that is optimizing the training for a given initiative or project. 

Although this is a somewhat old-school approach, we'd like to see some common building block approaches to certain things. We do a lot of coding and swapping things because there's a lot of common non-functional capabilities we have to share based on our own company policies. In that sense, it would be helpful to have some sort of modular building blocks that are in some of these up-and-coming extensible capabilities, like how you interface the next level of security scanning code or cloud to cloud capabilities, anything like that would be an improvement. These are expensive things to build and give out for free. At least knowing what's in the headlights for the products together with some good specific industry demos would help, whether related to the financial sector, healthcare sector, whatever. There isn't a lot of that; as things stand, they're generally offering demos with people talking about how you could have a secure way of developing a code for a HIPAA mixed standards or whatever. More documentation on how to precisely use the solution, particularly in a given industry sector, would be helpful.

We use a lot of third-party monitoring and although the extensibility is there, a monitoring tool suite as you get in production would be helpful. 

I've been using this solution for 10 years. 

This is a good product, it's served us well. I don't really have a lot of issues with it so I rate the solution eight out of 10. 

Currently, we're using it as a tracking tool. It helps our development department operate more efficiently while enabling the business side of the company to understand and track things better. For example, if we get a requirement from the business side, they don't tell us the status of the current cover every time. So basically what we do, if we complete development or make it to the development phase, then we can change the status in Jira. If the other departments want to see the progress, they can go to the Jira dashboard. So this reduces the amount of necessary communication between the business side and developers. Developers can mainly focus on the development instead of having to answer questions from other departments.

When we get a sign-off for a management request, we must catch it in our email inbox. Now we can get the sign-off through Jira, and I've automated this. For example, we can get the Jenkins pipeline results for every build we create and have that result plugged into Jira. So when we run the Jenkins pipeline, the build is already automatically connected to Jira. We've been able to integrate the ecosystem we created using this automation tool. If you open Jira, you get the development tab there, so you can find out everything a company made under this Jira or what brand is created under this Jira. As a developer, I find this feature valuable.

Jira could be simplified and integrated more with standard corporate communications tools. Say, for example, we have one indication of Jira in Confluence. So if we type a Jira ID into Confluence, it gives us all the information about the Jira profile. I would like to see this feature integrated with email platforms so we can just put our Jira ID or Jira link into an email and get all the details automatically. This kind of integration and automation would be helpful. 

I'd like to see better note-taking capabilities so every user can get notes when someone provides comments on a Jira ticket. So if they don't want to provide the comments on the Jira ticket, they can get the personal notes in a Jira tool for every profile. It's not something for the business side, but developers can track what work is finished and what still needs to be done. Jira could integrate better with Jenkins, which isn't fully supported on the Jira dashboard yet. I think it would be good to monitor the build's progress directly. That way, we don't have to attach it. We can do it from the background. Some workflow customization would also be good.

In the initial phase, I was using Jira for development and testing purposes. A story was assigned to me, and I just changed the standards and everything. But in the past six months, I have worked with configurations, adding different workflows, and all the other features.

Jira is pretty stable most of the time. However, we have an intranet on our side, and sometimes there are too many users. My company currently has four different departments at the top level. Each of the four departments has fewer than nine Jira users. My current department has approximately seven or eight users. So there are times when Jira goes down, and we find it difficult to log in. But we are trying to increase the capability of servers. Other than that, it's working fine.

We have migrated to GCP, and we're using the internal cloud servers, so we can easily integrate Jira into a server if we want. Scalability is a matter of cost. We just need to present our management with a valid reason for increasing capacity, and if they approve, it's an easy process for us.

We had to call Jira support for help with integration. For example, when I was trying to integrate Jira with my GitHub bot, I had to provide a specific kind of access and then run some scripts to find out if I had enough available space. After that, it's a smooth process.

The Jira setup is a bit complicated because we're deploying it in our internal servers. So we have to manage a lot of things ourselves. For example, when the new version of Jira comes in, we have to patch our servers and update our certificates. And then, for deployment, we have pipelines that we need to trigger. That's not too hard, but the patching and upgrading can be complex.

If it's a smooth deployment, it just takes 30 minutes because we only have to replicate it on a different server. So currently, we have more than 20 servers. So every time we deploy, we create a replica on every server, which takes time because we have to verify that it's working. In total, it's about two hours of downtime in Jira, so we do this at night. 

Currently, more than 10 people are involved with maintenance. For my team, I do the deployment and configurations. But if there is some fundamental change or a serious bug, a separate team handles this.

I don't deal with the money side of things. I just specify the requirements and the company handles everything. We are using it for many tasks so it seems like the price is reasonable. 

I rate JIRA eight out of 10. I think it's a great tool. I have been working with this tool for the past two years and I use it every day.

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 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.