"Workflow administration is an easy process, especially with respect to defects."
"We have the best community to support any problems that we have."
"The feature that I have found most valuable is that it is a quite powerful user tracking system."
"All departments can work with the same platform."
"The workflows are very easy to handle as far as scalability goes."
"Jira has a useful user interface and overall is easy to understand and learn."
"The board has been a very valuable feature because it can be very simple for teams that are not technical. It can also be highly technical and have lots of data for teams that are technical. So we use it for both instances."
"The UI is good. It's simple and not very complicated. It's very good for tracking."
"It is a well-integrated product in terms of the development lifecycle."
"It's got something that you won't find in other products."
"One of the main features is the user interface is very good."
"You can have test cases in DevOps but not in JIRA. And, DevOps has advantages in terms of executing those test cases."
"I like the entire tool because it is a one-stop-solution for DevOps."
"Great project management feature and Git-based repository."
"Fields can be customized and the reporting is good."
"The most valuable feature is the ease of use and performance."
"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."
"The GUI should have much better features like more graphical illustrations. There are some cases or benchmarks that we are trying to capture into a dashboard GUI's graphical summary, but unfortunately JIRA is not able to do that."
"There's a really steep learning curve for configuration."
"They are not supporting in-house servers anymore and I think I've got until January to port this to something else."
"The user interface is very detailed right now. It could be simplified if they consider targeting the user experience."
"They can maybe dumb down the directions for building the automation a little bit because to be able to build out the automation, I had to play around with it and learn what all the fields meant and what they were referencing. I don't have an IT background originally. My background is in biology, and I got into project management by chance. I am good at it, but I haven't really worked with coding languages. In terms of writing automation, it is easier for devs because they intuitively know what they're being asked, but as a PM who originally didn't have IT experience, it was a little bit daunting at first. It could also have an extra hierarchy to be able to allow tasks under stories. It could be the way it is set up at our organization, but currently, under stories, you can have sub-tasks, but you can't create a task. Being able to customize your hierarchy a little bit more would be beneficial because sometimes, the devs would say, "Well, here's a story, and now we need sub-tasks," but as we were building out the sub-tasks, sometimes we had to go a step lower to dig in a little bit more, and we couldn't do that."
"The reporting needs to be better."
"In Jira, say on the team, no matter the methodology, it doesn't matter what I'm practicing, if I am using the tool for a while and I've compiled some sort of history. If I want to change my workflow, say my team is today using to-do in progress done, and tomorrow, I decide I want to use to-do in review and done, and I apply that new workflow, I have just now effectively lost all of my histories in terms of reporting."
"It is not that intuitive. Sometimes, it is hard to find some of the functions. I would like to have an old-fashioned menu structure to be able to easily find things. Its environment setup is not very good. They should improve the way it is set up for different screens and make it easier to find functionalities and maintain team members."
"I think that the integration is to some extent, immature."
"The testing environment and different pipelining concepts can be improved."
"The solution can be improved by having better integration with other cloud platforms."
"I want DevOps to have more automated reminders about tasks that don't need management. We don't have reminders, so a project manager must track the tasks. It's not automatic."
"I would like to see a bit more project tracking."
"I would like to automate notifications on sprint planning. When we are getting to the end of sprint planning, we would be automatically notified."
"The portfolio is one area where DevOps has room for improvement. Built-in reporting and visualization also could be better. We're using Power BI and Tableau to compile more complex reports and dashboards. Azure DevOps has some out-of-the-box reporting capabilities, but they're very simple. It's usually okay on the team level, but if you have to run a complex report, it's difficult and insufficient, so we use Power BI as an extension."
Jira is ranked 1st in Application Lifecycle Management (ALM) Suites with 133 reviews while Microsoft Azure DevOps is ranked 2nd in Application Lifecycle Management (ALM) Suites with 78 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.
