We performed a comparison between Jira, OpenText ALM Octane, and TFS based on real PeerSpot user reviews.
Find out what your peers are saying about Atlassian, Microsoft, Nutanix and others in Application Lifecycle Management (ALM) Suites."A very comprehensive product; easy to set up and is very user-friendly."
"It was easy to use. The consultants that we had on board were familiar with it. So, obviously, having a community that had used it before or was familiar with it was a positive thing."
"The workflows are very easy to handle as far as scalability goes."
"We can create multiple boards for the same product backlogs."
"It also works well with all the integrated tools that you buy."
"I feel the strongest feature of Jira is its workflow engine. It helps us automate our workflows within our organization. It's the one characteristic of Jira which I think can help any organization, be it in any domain."
"The product's initial setup phase is easy."
"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."
"The way testing is closely tied into the product Backlog has made it more intuitive, or easier to manage the relationship between building out an application and testing it. In other tools, that is more segregated. The way it's designed in Octane, people have said it makes more sense to them, and that it's easier for them to understand their data and to maintain and test their solutions."
"We looked at all the market-leading tools, but we did not find anything quite as comprehensive as ALM Octane. When I say comprehensive, it's not just a single tool for Agile planning, backlog management release, sprint planning, etc., but it also has a built-in, comprehensive quality management module. It also has pipelines where we can hook up with our DevOps ecosystem/toolchain."
"It's more streamlined because we have it all under one umbrella. And once the business requirements and rules have been created, we can do test cases and apply them to the business rules."
"The solution natively supports Agile-Waterfall hybrid software development at an enterprise scale. This is very important to us. Because even though the company wishes to go Agile, we still have projects which follow a Waterfall methodology. In order for us to accommodate both, we needed some sort of hybrid system. Because if we are using a fully Agile system, then the reporting might not be correctly extracted."
"Micro Focus' technical support is good."
"The defect management gives us full-fledged capabilities for handling defects, including capturing the details of the defects and even screenshotting the defect cases. The defect management is comprehensive."
"On the user side, what I like a lot is the reporting capabilities. There's no tool, to my knowledge, that gets anywhere close to Octane at the moment when it comes to the reporting capabilities. I can do everything with the reporting. There's nothing missing. I have all the options. I can create graphs, including graphs of several types and looks."
"The integration points are very good. Octane gives us a window not only into our manual testing, but also our automation testing and our performance testing. We can see all results from all three streams of testing in one place."
"The solution is very much stable."
"The most valuable features of TFS are bug reporting and its high performance."
"Stability is okay."
"The most valuable feature from my point of view is project management, which includes user stories as well as task management."
"The most valuable features are related to source code management. Using TFS for source code management and being able to branch and have multiple developers work on the same projects is valuable. We can also branch and merge code back together."
"The solution's iteration board is good because you can track all your work with it."
"As far as queries are concerned, creating, grading, or customizing the queries as a primary requirement is very easy to do."
"It's user friendly. We haven't had any issues so far. It's flexible. If we need something, we can always contact the owner in our headquarters to make a configuration."
"The help desk and services management features are in need of improvement."
"For a non-technical person to use, Jira is not intuitive."
"There is a difficulty viewing all the attachments because they are shown in one place. I would like attachments to be shown at the comment level."
"The challenge which I frequently see from Jira is the label. When you search for a label sometimes, it suddenly disappears. If there's a mismatch due to all-caps or lower case, you won't be able to find it. It won't even come up as a recommendation or suggestion. That's something that can be really frustrating, as people create labels in their own specific ways and then no one else can find anything."
"I find the dashboard to be Jira's most problematic feature."
"One thing that I don't like about Jira is that when you do an export, it only allows a thousand issues. So the export feature needs to be better."
"It would be good if we can grant access based on the roles. This is something that Jira can look into. Currently, anyone with Jira access can access everything. Being able to define access based on the roles will give us more flexibility in managing Jira. I would like to have more reports in Jira. Currently, eight or nine reports are there. You can use Screen Test to get more reports or data from Jira, but you will have to get more add-ons, plug-ins, and stuff like that. It would be good if they can increase the number of reports."
"The performance and stability are visibly degrading since the database has been growing every year."
"The elements in filtering need to be improved, meaning the number of filters I can use in widgets or in the grid views in parallel. There's a limitation which bothers a lot of our users. Filtering in text, or having a complex filter is limited. In a given field, for example, I can use a filter only once. I cannot say, 'Include the values 1, 2, and 3, and exclude value 17.' This is not possible but we have requested it often."
"I like their smart analytics; perhaps they should continue to expand and improve there because it's a fantastic start."
"The Requirements Module could be better, to build up a better requirements process. There's a huge improvement from ALM.NET to Octane, but it's still not really facilitating all the needs of the product owners, to set up their requirements in Octane."
"The limitation of Octane is that we can't do a release outside of the sprint. We can only plan the release in the sprint. With Agile and JIRA tools, we can plan the release outside the sprint and do a global release of all the projects from the sprint."
"There are some challenges when we want to integrate the tool with other products, and it takes time for a team to figure out how to do it."
"Currently, Micro Focus ALM Octane is considered an old-world tool in the industry and lacks the perception of being a new-age tool among its customers."
"Improvements could be made by way of additional integrations across the lifecycle."
"Technical support can be slow."
"The tool needs improvement in stability."
"TFS is scalable with different Microsoft tools for test management but it is not scalable with other third-party tools."
"The solution is stable but could improve."
"I would like to see TFS improve its web interface as there are some limitations with IDs and the integration behind it and with open-source tools like VS Code."
"Access and permissions are confusing when attempting to include basic manual testing functionalities."
"The execution of test cases could stand improvement."
"The user interface could improve and test management was not useful in TFS."
"There are many things that I cannot do, and I have a lot of bugs."
