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 Microsoft, Atlassian, Nutanix and others in Application Lifecycle Management (ALM) Suites."The level of stability is quite good."
"The most valuable features of Jira are all the integrations with other systems. It's not the best in any specific area but it has lots of plug-ins and integrations."
"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 handles all of the issues that we need it to do."
"The most valuable features of this solution are workflow and reporting."
"Jira has been a good l tool for collaborating across large groups of people. The JQL feature is powerful and easy to use."
"It improved communication, as it was a popular tool, and most people enjoyed using it."
"JIRA stores history of changes, which helps a lot to track who, when, and why the issue was modified."
"It's brought our entire team into a single tool. We're all looking at the same real-time data. Our project management office has been able to set up dashboards for individual teams, and do comparisons by teams, of integration, and cross-team integration, burn-up, burn-down, and cumulative flow..."
"The filtering options are very good once you learn them. The document reports are also valuable. You can create reports in Word and PDF formats. That's very useful."
"A valuable feature is the pipeline, so that we can now connect to Jenkins and then have all the results from testing, from external, in the tool, so that we can see the whole approach from there. Also, We can work with labels so we have better filtering solutions than in ALM. And it's much smarter and leaner to use than ALM."
"Backlog management is the most valuable feature. This was a capability that was missing or difficult to achieve in ALM Quality Center."
"Its end-to-end traceability is one of the big advantages. Most of our agile projects work in a closed team structure. We are seeing what is the flow, where we are, and what is the project milestone. So, it provides end-to-end traceability and good visibility of project milestones."
"The feature I found most valuable in Micro Focus ALM Octane is its ability to integrate with the CI/CD stack."
"People really how easy it is to customize. In some previous tools, that has been very limited, or you had to know how to write code to do some of the customizations, or it was very confusing. Going back to the user interface, they've made the customization of the tool, the workspace settings, very easy for people to figure out and use."
"It is a very stable solution. Stability-wise, I rate the solution a ten out of ten."
"I like the build management features and the integration with Jenkins and many other tools."
"I like the Kanban board. It is very useful in terms of seeing who is working on what and what the current status of work is."
"The biggest value-add is the solution integrates well with most Microsoft products."
"Work item management integration with source control."
"The API for managing TFS programmatically is very powerful, you can listen on work items changes by TFS events."
"The solution is very much stable."
"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 interface is good with TFS."
"The Classic UI is a little bit messy. UX experience is also a little bit messy and is not according to the expectation of a tech user."
"Some small issues with stability."
"I have noticed a problem with Jira in the Philippines. In the Philippines, there are only a few companies that offer local support, which is alarming."
"We'd like to use it with non-Agile projects in the future, however, right now, it is a very Agile-focused product."
"I have had problems with performance and unresponsiveness. All of a sudden, the performance slowed down, and I had a number of users that could not use the tool."
"It would be very useful to have drag and drop time tracking."
"The solution needs more integrations with Azure DevOps OnPrem."
"It would be very practical if you can more freely reach the information that is already inside the system. Currently, we have to buy add-ons for it. There is a lot of information in the Jira system that you can handle only through add-ons. You cannot reach such information on your own. If you want to use this information, which is already in the system, you have to buy some add-on to use. For example, information about how much time an assignee is spending on a ticket is there in the system, but you cannot access it without an add-on. JQL is a very good way to reach the data inside Jira. If we can reach more objects, even through JQL, it would be great."
"Improvements could be made by way of additional integrations across the lifecycle."
"What could be improved in Micro Focus ALM Octane is its integration with Jira."
"The reporting is lacking from a requirements matrix and a traceability perspective."
"The biggest problem with ALM Octane is that it's very complex, so it's difficult to use and scale."
"There's a trend in our requests to have the ability to export data, en masse, out of Octane. There are capabilities within Octane to export data, but there are specifics around test suites and requirements and relations, as well as certain attributes, that we would like to be able to export easily out of Octane and into a database or Excel."
"There is an opportunity for them to do a little more with the dashboarding. We still feel that HPE Quality Center/HPE ALM reporting is very powerful. We talked with R&D, and there are some things on their roadmap, but at the same time, their strategy is to connect Octane with visualization tools such as Power BI."
"I have yet to experience the CI/CD part of Micro Focus ALM Octane but as demonstrated by the team who is providing the services, I see that the CI/CD could improve. When we check in the code, for the code snippet that has been checked in by a particular user, you need to open a separate file. When comparing Micro Focus ALM Octane to Jira, they have a separate window in which you can click on the ID and the code is visible in the snippet. It's a two-step process in Micro Focus ALM Octane and it's a single-step process in Jira. It's essential for the developers to think about this difference."
"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."
"They have room for improvement in merging the source code changes for multiple developers across files. It is very good at highlighting the changes that the source code automatically does not know how to handle, but it's not very good at reporting the ones that it did automatically. There are times when we have source code that gets merged, and we lose the changes that we expected to happen. It can get a little confusing at times. They can just do a little bit better on the merging of changes for multiple developers."
"Currently, we are looking for a solution with which we can incorporate third-party development sites or third-party project teams into the system. Because it is on-premise, it is a bit problematic because we need to have a VPN or something else in the system. A cloud-based solution would be better for us, and that's what we are looking for. Our biggest problem is the external connection, which, of course, is limited by our own IT. It would be good to have some kind of publishing service for this external connection. It might be there, and it might be that our IT is making it impossible for us. Its template editor could be easier to use. Currently, customizing the project templates according to your needs requires some work."
"Since it is Microsoft, it is technology agnostic, thus it does not really fit into various different technologies in the organization."
"We are also using Microsoft Teams. The two products function separately. There is not enough collaboration between Microsoft Teams and TFS."
"There are many things that I cannot do, and I have a lot of bugs."
"The test management interface is not very handy."
"We encounter issues with backups."
"The solution's server for deployment needs to be improved."
