Jira Reviews

We primarily use the solution for customer service and managed services, and for all the workflows for the services. It's also a bit of a CRM. We use it largely for technical support.

The solution provides an integrated platform for customer service. It's good at organizing our technical support for clients.

The solution has been very stable overall. We haven't had any issues with performance.

The pricing is reasonable. It's not too expensive.

The UX and UI could be better. It's something they need to improve upon. It needs to be updated and made more modern.

It would be ideal if the solution could be available as a mobile application.

We would like the solution to be a little less costly, although, overall, the price isn't bad.

I've been using the solution for five years or so. We've been using it for a while at this point.

I've found the stability to be very good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable and the performance has been good.

We've never reached out to technical support for help in the past. I wouldn't be able to speak to the level of service they provide.

We did not previously use another solution. We do not want to switch to something new at this time either.

Unfortunately, I was not a part of the company when it was originally set up. I have no idea how the implementation went. I wouldn't be able to comment on if it was easy or difficult and/or how long it took to deploy.

While, of course, in general, we always want the pricing to be lower, it's pretty reasonable. The costs aren't too bad.

We are just a JIRA customer and an end-user.

We are using the latest version of the solution. I'm not exactly sure of the version number.

We do not plan to switch to another solution. We're quite happy with this product overall.

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

The ability to keep stories, bugs and documentation in one application is a valuable feature, as is the ability to easily create swim lanes for organizing work.

As everything is within one application, it is easy to write end-of-sprint reports.

It worked fine for my requirements.

Stability: we encountered occasional timeouts.

I have used this product on and off for about seven years.

I did not encounter any deployment issues.

We encountered occasional timeouts.

I did not encounter any scalability issues.

I did not need to contact customer service.

I did not need to contact technical support.

I have not used any other solution, before this product.

The setup was very straightforward.

We have implemented this product in-house.

This product is easy to set-up. There are many add-on applications to assist you further to manage all requirements such as Confluence for document control, Capture for testing, etc.

I am the software developer manager and I use Jira to manage team performance. We're also starting to use Jira for our drives. I used Jira before, for creating user stories from boards, to discuss issues, and many other tasks. Today we use Jira, Confluence, and BitBucket in our work. We practice scrum in our organization.

It improved with many exiting features to manage user stories, planning and retrospective meetings very productive.

The documentation is very good.

The solution is stable.

You can scale the solution easily.

It's comparable to Azure DevOps.

It's a very complete product overall.

It would be ideal if Jira had future functionalities to integrate more easily with various aspects of code reviews.

It would be nice if, in the future, Jira worked a bit more like Azure DevOps in order to be able to manage work in progress and have the task measurements in strategies for the stories.

In the future, I would like to have traceability features. For example, when you create a task or a sub-task that's related to code. In this task, if we could create a method for retrieve customer information, that would be helpful. In that case, I would want to train with the source code later.

I'm new to the company. Although I've worked with Jira before, I've only been at this company for one week.

Atlassian solutions for me are very good solutions. They are very interesting and very productive. As a user, it is necessary to have a unique portal to make traceability between sub-tasks related to code or programming. You can create and screen or implement a function or a class, related for example to the code that you are pushing in the repository or commit in the repository. If I open the sub-task, I will see the code related to the sub-task. It's very similar like Azure DevOps. Azure DevOps, however, has this functionality for traceability. This functionality will be amazing that Jira would implement something similar.

I prefer to use Azure DevOps instead of Jira for stability or the frequency of use. In my case, for example, I feel that more users, more companies don't think Azure DevOps makes a good choice due to the fact that the cost is higher than Jira.

The scalability is very good if you're carrying a lot of projects here, and if the company needs to have a lot of people to PEA development centers in Mexico. Our technicians can easily test the tool and scale it in order to develop projects.

We do plan to increase usage. We're already training more users. We're increasing quickly so that our teams will be ready for upcoming projects.

We have manuals, technical support, and also technical specialists in the company. I haven't had the opportunity to use directly call the technical support from Atlassian, however, the technical documentation that I have reviewed is excellent. We're satisfied with the level of service we have access to.

We also use Azure DevOps. They are both very similar. The main difference is Azure offers traceability.

The solution is easy to implement. We have the cloud version of Jira in the company, and we don't worry about maintenance, it's automatic.

The cost of Jira is okay. It's better than Azure DevOps. We don't have any licensing fees that I know of.

While I'm new to the company, it's my understanding that it is a partner of Atlassian.

We use the latest version of the solution, as we use the cloud, which updates automatically.

Our company has both Azure DevOps and Jira. I use Jira, and Azure DevOps is used for other purposes. Most projects, all projects that are using Azure DevOps are legacy projects. The new projects and new solutions are using Jira.

On a scale from one to ten, I'd rate Jira at a ten. It's a very good product.

Both tools, Azure DevOps and Jira are at the same level. In terms of preference, I typically choose Azure DevOps for familiarity but not for features. For features, both are the same. For example, Jira has amazing features that Azure DevOps doesn't have, and also Azure DevOps has the flexibility that I like very much. Both tools have different interesting aspects. However, if Atlassian would implement traceability, I would prefer to use Atlassian. For me, it's more complete and allows for smaller teams than Azure DevOps.

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.

It is easy to assign books, story styles, move across platforms and to different stakeholders while using this platform.

It has an easy UI that can easily plug-in to every level.

The CACD solutions on JIRA has some plugins, but they are not easily understandable or workable. 

It is definitely a stable product.

The scalability is fine.  

Tech support is good. 

We had a JIRA administrator help us with the setup, as well as an administration team. It took a bit of time to integrate the JIRA to our system.

In comparison to other solutions on the market, it is cost-effective. 

We looked at Micro Focus ALM vs JIRA, but it was quite expensive in comparison.

It is a user-friendly solution that is simple to use. 

Our testers and QA teams use this tool. 

This solution is easy to use and takes a lot of burden off the QA team.

I'd like to see a more stable product with more integrations, as new products are coming on the market daily.

.

The technical support could be better, a little more customer friendly and knowledgeable.

The initial setup was quite straightforward. We had our technical team deal with it. We currently have around 25 people using the product. 

We pay an annual licensing fee. 

I rate this solution an eight out of 10. 

We use one version of Jira internally and we also have another version of Jira that we use externally for our customer. We've been using it for both.

Internally we use Jira for our own implementations and capturing requirements and our customers are using the whole tool for the whole software development life cycle. They're using it for the full life cycle of the product.

The Defect section could be improved. When you're trying to keep track of the requirements and the Defect section, this setup could be done better.

I was struggling to set it up. I wish the whole workflow process was easier to set up. You put the requirements in and then you send it to the developer. They get a notification. Then they go into Jira.

We have been using Jira over the last 12 months or more.

On a scale of one to ten, I would give Jira a seven.

To be a ten, there should be more options where you just click and drag. That would be nice. It's hard to copy and paste requirements. You lose your formatting and everything. So just simple navigation stuff should be improved.

We use JIRA for maintaining tasks and bugs. Overall, we love using JIRA because it performs very well with a lot of tasks and a lot of dashboards.

Having a tool to manage all your tasks and all your bugs is very useful for any company. We use it a lot to keep track, to see how our development is going and how automation is going.

We use a lot of dashboards and a lot of queries to search for specific bugs related to specific versions. Also, we can provide it to all of our users throughout the company.

The ability to change and rewrite tasks is valuable. You can add a lot of columns, change the owners and the change the components. It gives you a lot of flexibility between the teams.

I would like to see it connecting to Git. That could be useful. We use it for Stash, but I think there is one for Git also. I don't know if it's a plug-in that exists already, but that could be nice.

We have had no problems with stability. We're doing maintenance upgrades, but it has working well all the time.

We're not dealing with the scalability because we're not IT, but I don't think there is a problem with scalability.

We used Bugzilla but its UI was not as user-friendly. The end-user experience was very basic because it's a free tool. It's important to us that QA be able to track the issues and, of course, for the developers to be able to track all the tasks. So we're looking for the balance between performance of the user interface and the UI for the other workers in the company.

I would rate it at nine out of 10 because there is always room for improvement, but we love this tool and we use it a lot.

I would recommend JIRA. Compare all the tools for bug and task management. After that, you'll see that JIRA is by far the best.