We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
"Jira is very useful for project management for internal projects."
"Most of my work is keeping track of what's been going on and identifying what is blocking future work. What I like about this solution is you can create a consolidated customized dashboard out of your files to identify what's been going on and identify who has how much data assigned to them."
"It is very straightforward and easy to use."
"There are many good things about Atlassian."
"The solution offers a lot of plugins."
"Jira is flexible and accessible for the end-user. It lets users track their requests. The look and feel are good for our purposes."
"This is our way of communicating with different teams. We are a global company. I am based in San Diego, for example. A lot of the BAs are based in Paris. The development team is based in Minsk. We absolutely need to be in constant communication and on the same page."
"The feature that I have found most valuable is its ease of use. I don't need to train anyone to use it, I just give them access and they can use it to add comments, move their issues, change the status, monitor, read, and so on."
"I like the fact that there is built-in Power BI. Both are Microsoft tools. So, you can incorporate dashboard capabilities."
"I really like the Microsoft DevOps survey."
"This solution works with other Microsoft solutions pretty easily. It was easy to integrate everything into all the other tools that we were using. It integrates very seamlessly."
"Monitoring is most valuable."
"The most valuable feature is that it brings order to our projects, and we know the status of each one at every moment."
"What I like the most is the DevOps Boards. It's easy to create a hierarchical project structure, assign tasks to people, and to track their tasks."
"We are able to generate many different types of reports from Azure."
"We can eliminate some of the middleman processes."
"Jira could be more, for example, like Micro Focus, which is what I mostly work with currently."
"I would like to see additional possibilities for reporting."
"It is not capturing the number of hours for which each person has worked on certain things. We use many add-ons to let resources enter the time in the user story itself. We use an add-on called Tempo, but it is kind of a lousy add-on. It is not straightforward. Rather than helping us, it creates a lot of confusion. So, instead of looking out for the additional add-on, I would prefer to have the timesheet entered as a part of Jira itself. They are anyways capturing every information they could for each user story, and then we are able to break down all the task lists. For each task, we're also assigning a resource. So, while we're doing it, why can't they allow the users to enter the time that can be created as a report? Right now, we need to acquire the add-on, and the add-on is not great. It is not helping. The add-on is also not free."
"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."
"Could offer an improved user experience."
"There needs to be easier integration with third-parties — personally, this is the biggest issue for me."
"Jira has recently updated their UI, but more can be done to make it even better."
"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."
"The testing environment and different pipelining concepts can be improved."
"Not all companies use the same methodology which could limit the use of this solution."
"They should expand it from just a PC, software, or server development platform to other kinds of software or engineering systems so that it is not necessarily built around a normal PC with a server. I would like to see the ability to write my own scripts in my own compiled program or online. Right now, there are things that you can do in the user interface, but you can't do them programmatically and vice versa. I want to see them both. If I can do it in a script, I should be able to do it from the user interface, and if I can do it in the user interface, I should be able to do it in a script."
"I would like to see new features added."
"I would like to see DevOps have the ability to give us something with a compatibility or traceability matrix."
"I would like to see better integration and collaboration between tools."
"The tool was developed for Agile project methodology, but I've noticed that there has also been a try to incorporate what is typically done in MS Project, which is for more sequential Waterfall projects. The problem with that is that it is half-baked for Waterfall projects. If you're going to do it, then either go all the way and allow us to use the tool for both or don't do it at all."
"Definitely, there should be more integration between GitHub and Azure DevOps."
"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."
"Its price is fine, but we would like it to be less expensive. We are paying on a yearly basis."
"The price at the moment for Jira is okay. I'm absolutely not amused with the plans to try to drive us to the cloud or to other licensing models. For the very simple reason that we are a company in the defense sector where cloud is problematic in a number of the domains. We are now approximately 60 users and the new policy will actually confront us with an upscale to approximately 500 users. I find it unacceptable, and may potentially lead us to look for another solution."
"We are on an annual license and could be less expensive."
"There are no additional costs to the standard licensing."
"If you are using just Jira, it is cheap, but if you start to use it and you feel you need some more services or more functions, then you have to buy add-ons, which can make it expensive."
"There is a monthly license required for this solution and it is expensive."
"There are other solutions that are free making this solution seem expensive in comparison."
"The licensing structure is good."
"We pay a monthly license for Microsoft Azure DevOps."
"I am not aware of any licensing subscriptions for the solution."
"Most of the things that we need and use are incorporated in the corporate solution — there are no additional costs."
"It is a subscription model and I only pay for what I use."
"I don't know what we pay, but I do know what I've seen online. If we switched to JIRA, we will basically have to double our costs because we still have to pay for the DevOps licensing. We're probably spending $100 a month on it. It has only standard licensing fees."
"There are additional costs for some functionality, such as increased scalability."
"I don't have a problem with the pricing."
JIRA has multiple deployment options to provide the flexibility your organization needs.
Cloud is a fully hosted service for customers who want to iterate quickly and have us take care of managing the infrastructure.
For customers who need to run our applications behind their firewall, we have Server and Data Center options. Server delivers greater capacity for a larger user base and gives you more control, allowing you to remain compliant with your enterprise IT, security, IP and privacy policies. For our largest customers, Data Center provides all the capability of our Server option, along with high availability, instant scalability and performance at scale.
Atlassian also offers premium support and strategic services for enterprise customers. Technical Account Managers are cross-functional technical advisors providing proactive planning and strategic guidance across your organization. Premier Support goes above and beyond our standard offerings to give you account-wide support from a team of senior support engineers.
Azure DevOps Services is a cloud service for collaborating on code development. It provides an integrated set of features that you access through your web browser or IDE client, including the following:
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 118 reviews while Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 69 reviews. Jira is rated 8.0, while Microsoft Azure DevOps is rated 8.0. The top reviewer of Jira writes "Great for collaboration, very stable, and extracting data is straightforward". On the other hand, the top reviewer of Microsoft Azure DevOps writes "Robust functionality, good integration, continually enhanced, and easy to scale". Jira is most compared with Micro Focus ALM Octane, TFS, IBM Rational DOORS, Rally Software and Micro Focus ALM Quality Center, whereas Microsoft Azure DevOps is most compared with GitLab, TFS, ServiceNow IT Business Management, Red Hat Ansible Automation Platform and Micro Focus ALM Quality Center. See our Jira vs. Microsoft Azure DevOps report.
See our list of best Application Lifecycle Management (ALM) Suites vendors.
We monitor all Application Lifecycle Management (ALM) Suites reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.