Jira Reviews

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.

We are using the solution for project and defect management, and task tracking.

There could be some improvements in the project management and portfolio level features. I think they could bring more flavours of Agile to Jira, that would help.

I have been using the solution for approximately eight years.

We have found it to be very stable.

The solution is very scalable and flexible. It's one of the best products that we have been using. We currently have 80 users using the solution.

The configurations for the installation are very well documented on Jira sites. You can just go there and it has everything you need. The installation did not take much time, it was straight forward. 

We had one internal administrator do the implementation, the configurations are straightforward.

I would recommend this product to others. 

I rate Jire a nine out of ten.

We primarily use the solution for bug tracking. It's for customer support purposes.

The solution is quite easy to use. It's very user-friendly. The product is very easy to understand.

The solution offers very good tools for Agile teams.

The pricing of the product is very good. It's not too expensive.

We're more focused on other solutions. Jira could be more, for example, like Micro Focus, which is what I mostly work with currently.

I've been using the solution for about seven months at this point.

I'm not sure if the product is stable or not. I don't have any insights into that aspect of the product.

I don't know if the solution is scalable or not. It's not an aspect of the solution I'm responsible for.

I'm not sure how many users are on the solution currently. I'm not sure if there is a plan to increase usage just yet. That might be a question for our company in the next year or so.

We tend to handle technical support internally for the most part. I can't really speak to the actual technical support from Jira as I haven't dealt with them for the most part.

We are also using Micro Focus.

I'm more on the customer support side of the product. I didn't really handle the setup process. Other members of my team handled the implementation.

We've found the pricing to be quite good. It's not overly expensive. It's very reasonable and affordable for companies to implement.

We're just customers and end-users. We don't have a specific business relationship with Jira.

I'm not sure of which version of the solution we're using currently. It's my understanding that it is the latest version. I'm not sure if we are using the cloud or the on-premises deployment version.

Currently, I'm more focused on the Micro Focus product as opposed to Jira. That's more where my expertise is at the moment.

That said, it's pretty easy to use and I would recommend Jira to other organizations for that reason.

Overall, I would rate it at a seven out of ten.

We are using Jira for tracking and management.

It's an open-sourced product that is easy to customize.

Stability is an area of concern and it needs improvement, otherwise, it's a good product.

In the next release, it should be more stable and have more APIs to integrate more plugins with it.

The first time that I used Jira was in 2011. 

I am using the older version that was released in 2019.

It's not a stable solution.

The number of users is in the hundreds.

We will not likely continue using this product. Our customers are evaluating other solutions that are more stable and scalable.

We have not contacted technical support.

Previously, we did not use another product.

The initial setup is straightforward. 

The migration took a week to complete.

Depending on the use cases, I would either recommend Jira or not.

I would rate this solution a six out of ten.

Right now, I'm just trying the solution out. I'm doing a POC.

The solution helps a lot with scrums.

It's great for development. 

The documentation is quite good.

It has some automated software testing which is useful.

I'd like some more features around software testing. I'd like to see some more stuff done around data testing. That's what I'm most interested in.

They could be better around generating documentation and essentially helping with test scenarios, test cases, or test results in a way that is more user-friendly.

The product needs to be more flexible to adapt more effectively. Sometimes you fix the style or the format and it might not suit the environment. I'd like to be able to more effectively configure it.

I've only used the solution for less than a year at this point. It hasn't been too long.

The solution is quite stable. It's not really buggy and it doesn't crash or freeze. It's pretty reliable.

The product can scale if a company needs it to. They should be able to expand it to have it meet their needs.

I haven't really dealt with technical support. I study the solution mostly on my own. I've never spoken to them and therefore can't speak to how their services are.

In a few months, once I have used it on a deeper level, I may get the chance to reach out. However, as of right now, that has not been the case.

The initial setup is not complex at all. It's quite straightforward. We didn't have any issues with it.

I'm not sure how long the deployment takes. I'm a lecturer and consultant, and therefore my role is more to help people use the tool rather than set up the tool for them.

I use the free version of the solution. We don't pay for it at all. 

I use the current version of the solution.

Right now, I'm on the free version. I'm just trying it out right now, to see if I like it.

I would recommend the solution to other organizations.

Overall, I would rate it at a seven out of ten.

I use it for project management and agile scrum projects. I am a manager, and I work with backlog tools and sprint plans. I only use Jira for backlogs, sprint reviews, and data reports. Our project manager is the person who is really working with Jira along with the team. We also have Confluence and Bitbucket. We use CloudBees and DevOps for the deployment of the environment.

It is easy to deploy in the cloud and other environments. It is also easy to view the reports of the sprint review or the sprint plan and the relation between the backlog and the repositories.

I am not sure if Jira can be integrated with our ERP. We have our ERP for the cost estimates or measurements. It would be nice if we can check or view a plan with the real cost. Currently, we have to do a double check of costs. It would be better to be able to integrate it with Jira.

I have been using Jira for almost one year.

I don't work too much with Jira. I use it only to see the reports, and I don't feel that there are many bugs. It is stable.

It is not too expensive. It is just comparative to other tools like Microsoft Teams.

I would recommend this solution. We are interested in migrating to Jira and using it as our internal tool for agile projects and for controlling the IT software development cycle for projects like consulting or API. It will be more used for agile projects. It is a good tool. We also have the latest version of Microsoft Teams, but it is limited. It is better to use Jira.

I would rate Jira a nine 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.

Our primary use case for JIRA is for entering user stories into the login books.

The most valuable aspect of this solution is its ability to connect everything together. 

It also has good stability. 

I have to go through a lot of processes to consider it done. I have to log in then change the logins and make it interesting. There shouldn't be the need to go through this. The process should be improved. 

It's not so good for testing.

I have been using JIRA for ten years. 

It has good stability until now. 

You can scale with it. 

We have around 35 users. 

I haven't needed their support. 

I previously worked with TFS.

There are a lot of similarities between the two. Especially in terms of working in the same field, tracking issues, and tracking bugs.

I would recommend JIRA to somebody considering it. I love working with it. 

I would rate it a seven out of ten. In the next release, they should make the process easier to be customized.