Jira Reviews

It's scalable.

It's easy to deploy.

The cost of the solution seems to be reasonable. 

Once the solution is deployed, it's not easy to configure. If you have a lot of capability, it's very dynamic from the back end. Therefore, when setting up the workflows, it can be a little bit complex. We did a lot of functions on managing the development and that's why maybe it's a little bit complex. Basically, in order to design a workflow in Jira, it's not a straightforward task.

From a feature perspective, not much is missing. However, they need to put some investment into the user experience. It needs to be easier to use, more friendly, especially on the configuration part. It's a hassle. You need to deal with a high learning curve in order to understand how it's configured and how it can work.

We've used the solution for more than eight years now.

The solution is scalable. 

We have more than 50 people using Jira at this time. 

We do plan to increase usage. We are growing. Since we are growing, we are increasing Jira as each member on the technology team needs an account for development, business analysis, or testing.

While the initial setup is pretty simple and straightforward, handling the configurations and the workflows can be complex. 

I didn't attend this in the development phase. In testing, I did the same effort and it took me a month to set up while I was deploying a test stream. I worked on the testing workflow as well, the defect workflow. That said, I don't know how long it takes for them to configure Jira.

We handled the setup in-house.

The licensing is per unit. My understanding is that it is pretty affordable. However, I don't directly deal with licensing.

We are just a customer and an end-user.

From a testing point of view, I would rate it at a six out of ten. I use it as a defect management tool, and it, for me, it's not easy to use.

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

Most of our company is using Jira for IT projects. We had an internal project with which I was involved, and I touched on it a little bit. We have its latest version.

I liked the flexibility of the application. It was pretty user-friendly.

If you're not a technical person, it might not be very user-friendly.

I have been using this solution for the past 12 months.

It was stable. I don't recall any bugs or glitches.

My impression is that it was pretty scalable. We have 10 to 12 people who use it. They are IT managers, directors, and developers.

I did not have to use tech support.

I used to use Microsoft Project in a different organization. In my current organization, I have been working for two years, and Jira is the only tool that they have used as far as I know. They are two different animals.

I wasn't involved in its setup.

I would rate Jira an eight out of ten because of its flexibility. I like the controls on it.

We primarily use the solution for collaboration purposes.

The solution has basically been problem-free so far.

Overall, we've found the product to be quite flexible.

The level of stability is quite good.

The product can scale if you need it to.

I'd like the solution to be more secure.

I've been using the solution for about six months at this point. It hasn't been that long. I've been using it for less than a year.

We've enjoyed the stability of the solution. It's good. It doesn't crash or freeze. There are no bugs or glitches. The performance is reliable.

The solution can scale quite well. If a company needs to expand it out, it can do so with relative ease. It's not a pronblem.

Not too many people use the solution in my organization. There are fewer than ten users right now.

We do not have any plans to continue to use the solution, let alone increasing usage.

I've never directly dealt with technical support. There was never a need to call. Therefore, I can't speak to how helpful or responsive they are. There was never an opportunity to interact.

We did not previously use another solution before implementing Jira.

I didn't handle any aspect of the installation, and therefore I can't speak to how easy or difficult the implementation was. I'm not sure how long the deployment itself took. I was just handed my login and I was good to go.

As I wasn't involved in the installation process, I can't speak to if a consultant or integrator was used. I have no knowledge of that being the case. 

I can't speak to how much a license costs or the process behind setting one up and renewing it. I just use the solution. I don't handle sales or billing.

I'm just a customer and an end-user. I don't have a business relationship with Jira.

It's my understanding that we are using the latest version of the solution, however, I am not 100% positive that is the case. I don't know the version number off-hand. I am also not sure which deployment model we are using and if it is deployed on cloud or on-premises.

I'd recommend the solution to other organizations.

I would rate the solution at an eight out of ten overall.

There are so many use cases for Jira. If it's got something to do with IT, it will be covered by Jira. They have a very extensive marketplace and you can find nearly every solution there, including version controlling, source control for the code, automation, test automation, security scanning, configuration, and development management. 

What I find valuable about Jira is that it's an ecosystem. Sometimes, it does not provide the best-in-class solutions, but it's so well integrated. You will not have many problems with integration.

The transfer of the functionality between testing or pre-production and the production environment could be improved. It would be helpful to have more automation in this area.

I have been using this product for three years. 

In general, the core of the product is very stable.

Approximately 150 users use this product at our company. One comment I would have regarding scalability is that I noticed Jira is not yet ready for the Docker platform. I think they are working on this and it will improve the scalability of the product. 

Overall, their support is okay. Many topics are covered in their documentation or on Atlassian. We receive support from a local partner.

We previously used SISA. 

The initial installation was straightforward for us. What could be improved is the migration between the testing and production environments. This could be automated somehow as the manual transfer of certain workflows and functionalities is very time consuming right now.

We mainly use Jira software, including Jira Issue Manager, for bug tracking and project management, and have done so for over a decade. Then in the last six years we have also used Jira Agile in a lot of our project management work. We use the enterprise version of Jira.

There are a couple of things that I find valuable about Jira, the first being its architecture. For instance, I like that you can create dashboards easily, which makes it very user-friendly. You don't need much training on that. You can just get right to it and people are able to use almost all of Jira's features with little training.

The simplicity of Jira is the part that I like the most, as well as the way in which it can be extended. For example, I like that you can send data to and from Jira easily, and it integrates well with lots of third-party plugins.

In terms of improvement, I think Jira (Jira Agile, specifically) can be made more user-friendly. Most of the time, when people are somewhat used to the process, they find it easy to work with. But the thing is, if I want to create a sprint, I'd like the ability for it to come out like a kind of board or something like that. For example, they could offer something like a wizard for users who want to quickly create a sprint on the spot with a few clicks. I think that could be useful.

When I first started using Jira and we were in the middle of coming up with a solution, I found that there could be better separation of tasks when it comes to user stories and epics. For example, right now we can take users and sub-task them, but the developer is not able to easily ask for or request a task as a separate thing to work on.

Other than that, I would definitely appreciate more kinds of features in general. But we have already requested these from Jira ourselves with their voting system. These requests are in their backlog now and we hope to see them in future soon.

We have been using Jira for more than ten years.

I feel it is quite stable, not least because it has been around for a long time. For the last few years, we have never see any issues from our location or any other location that our people use it from.

We have never had to use Jira's support as far as I know. 

I wasn't fully involved in the initial enterprise setup of Jira, but I remember first trying out some of the plugins on my laptop and I found it all rather easy. And for the people in charge of the main setup, they were able to install it and set it up quite fast.

We are using the enterprise license which is nice because it ensures that we always have the latest versions of Jira software. 

I would definitely recommend Jira for project management and similar uses, as well as other products from Atlassian like Bamboo.

Jira isn't what you would call a "coded solution" for scrum or anything like that, but it's able to do a lot of different things for people who are looking for that kind of thing. If you are looking for a custom-made solution specifically for agile or scrum, then you can go try other products like Valley or others. But if you want a good general-purpose project management system with solid integration solutions like Bamboo, then I think Jira is the product for you.

I would rate Jira an eight out of ten.

Our primary use case for this solution is work management and task management.

We use this product quite extensively, and we're planning to roll out a module for the Accounts Department to be able to map manpower costs to project work, directly. That is something that we're working on right now.

Based on the flexibility that it offers us, we can adapt to different projects with different cycles. Based on whatever cycle we are working on for a particular project, we can configure the solution to suit us. This helps us to manage the work, essentially in one place, and we have visibility of all projects that are going on in the company.

The most valuable feature is the flexibility of the configuration, being able to configure it to suit your own needs.

The plugin management needs a lot of work. Sometimes you have issues with plugins and it stumps the vendors, as well as the Atlassian support.

I think that more extensive reporting would be very good because sometimes it is a hassle for us.

It is pretty stable. I would give it a ninety-five.

In terms of stability, it is pretty impressive and I would give it ninety-five. We have not had any load issues.

We currently have between twenty-five and thirty users, whose roles range from Software Developer to Chief Executive Officer.

I would rate the solution's technical support an eight out of ten. 

I have used a couple of solutions, but I have used this one for my entire career in working with different teams. I have had to integrate my own solution as well, but the majority of my work has been using this product.

I have worked with both the hosted application and the cloud version. For the cloud, the initial setup is very easy. You can do it in basically two minutes and you're out but for the server, the setup entails a lot more.

This is quite understandable because you're going to be managing it by yourself, onsite. For the Cloud, it's pretty straightforward, but if it's the server version then you need a lot more focus and experience to be able to configure it correctly.

The last time I installed a server instance we had to do it overnight and it took me between four and six hours.

The deployment was done in-house.

There is no maintenance required for the cloud version.

I would say that we have seen ROI with this solution. When we are looking for some sort of information, it just makes our lives much easier because we are able to do things without having to talk to anybody. You know exactly what is going on. It limits personal interaction but helps us to get our jobs done quickly.

Licensing is on a monthly basis, and it is based on what you use. There is a base cost and then as you include other items, the cost rises. Our last payment was perhaps $1600, which includes both user licenses and add-ons.

There are no additional costs beyond the licensing fees, and it covers support.

Before choosing this solution we evaluated SmartShift for work management, and we also tried Trello.

My advice for anyone who is implementing this solution is to ensure that your in-house processes are clear. Things have to be clear, as much as flexible, because if it is not correctly configured then it could just be a mess. So, you have to be very clear on what your processes are in-house, and then based on that you can translate them into Jira.

Knowing in advance what kind of information you're looking for from Jira will help you in being able to set it up correctly.

I would rate this solution an eight out of ten.

The primary use case is task management within the team and the company, as well as version management and bug management.

It makes the work process transparent, visible to everyone who needs to know about the current state of the versions, and all that happens. It helps to communicate among different teams, like support, R&D, and QA. Everything is in one place and everything is communicated in the same form.

JQL, which is JIRA Query Language. I can filter all the issues, display the items as I want.

It's very flexible. I can define workflows and custom fields and dependencies between issues and projects. And every project can have a custom configuration with my fields, my names for fields, my validations, and my workflows. It's very customizable.

I'm using the old version. I haven't upgraded to the new one, so maybe a feature I would be looking for is already there. I don't know. Something I had been looking for was pasting screenshots into issue details, but this was already implemented in the new version. 

Better user management features could help.

I have no problem with stability.

I don't have problems with the scalability. I know companies that are much larger than just projects or teams, that are much larger than my current team, and they work with JIRA and it works well.

I used the support from JIRA several times and it was good. I had questions about licensing, I had questions about upgrading from an old version to a newer version.

When I am evaluating a product or vendor, I have some intuition about it. I see how the thing is built and works, and I go by my own impression. For me, that is important. And, of course, price and maturity of the product, along with flexibility, are important criteria.

I would rate this solution a 10 out of 10. It's an excellent product. It has already improved. It has good support. From the beginning, it was very smart and customizable and built well, works well. There are almost no bugs that I have discovered. It's a good product.

I just saw an advertisement on the street for a product called Monday.com. I read a few lines, a few words about it. I hadn't heard of it before that, but I understand it does something similar to JIRA. Obviously, I can recommend using JIRA but if you are searching for something else, the first impression I got from reading the home page of Monday.com was good, so maybe it's worth evaluating.