We performed a comparison between GitLab and IBM Engineering Workflow Management based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, GitLab, Atlassian and others in Enterprise Agile Planning Tools."I have found the most valuable feature is security control. I also like the branching and cloning software."
"For us, Gitlab's most valuable feature is the integration with Cypress. We're using Cypress as an automation tool, so we're using GitLab as a tool for running in parallel."
"As a developer, this solution is useful as a repository holder because most of the POC projects that we have are on GitLab."
"We like that we can create branches and then the branches can be reviewed and you can mesh those branches back. You can independently work with your own branch, you don't need to really control the core of other people."
"The most valuable feature of GitLab is its security."
"CI/CD is valuable for me."
"GitLab is being used as a repository for our codebase and it is a one stop DevOps tool we use in our team."
"I have had no problem with the stability of the solution."
"Traceability reporting is inbuilt and includes all your requirements."
"Work distribution among team members and accountability for completion with a clearer picture."
"Good for managing stories, sprints, hydration and releases."
"Agile templates give us a standard methodology for every Agile project. Also, the ability to create our own object types and linkages to features/epics allows us to enhance the verification of feature readiness."
"All of the features work together to provide a powerful holistic solution - from the dashboard all the way through to security."
"We can track the status of test cases (passed or saved) in a single view. Based on releases and other attributes, we generate various reports and extract metrics from the data."
"It would be better if there weren't any outages. There are occasions where we usually see a lot of outages using GitLab. It happens at least once a week or something like that. Whatever pipelines you're running, to check the logs, you need to have a different set of tools like Argus or something like that. If you have pipelines running on GitLab, you need a separate service deployed to view the logs, which is kind of a pain. If the logs can be used conveniently on GitLab, that would be definitely helpful. I'm not talking about the CI/CD pipelines but the back-end services and microservices deployed over GitLab. To view the logs for those microservices, you need to have separate log viewers, which is kind of a pain."
"The documentation could be improved to help newcomers better understand things like creating new branches."
"The price of GitLab could improve, it is high."
"I would like to see static analysis also embedded in GitLab. That would also help us. If there's something that it does internally by GitLab and then that is already tied up with your pipeline and then it can tell you that you're coding is good or your code is not great. Based on that, it would pass or fail. That should be streamlined. I would think that would help to a greater extent, in terms of having one solution rather than depending on multiple vendors."
"We are having a few problems integrating with Jira at the moment, which is something that our IT department is investigating."
"We have only seen a couple of issues on Gitlab, which we use for building some of the applications."
"The solution does not have many built-in functions or variables so scripting is required."
"There is room for improvement in GitLab Agents."
"Teams need clearer pictures of resource availability in charts and dashboards along with plans."
"Some administrative tasks are difficult to perform. These could be simplified."
"The solution is very heavily vendor dependent."
"Lacks ability to customize and reporting can be slow."
"We have encountered issues with stability. We have seen where the entire system kind of goes for a toss when certain people use certain types of queries, which are very costly. Then the system kind of slows down a bit, and we have to monitor it."
More IBM Engineering Workflow Management Pricing and Cost Advice →
GitLab is ranked 2nd in Enterprise Agile Planning Tools with 70 reviews while IBM Engineering Workflow Management is ranked 10th in Enterprise Agile Planning Tools with 14 reviews. GitLab is rated 8.6, while IBM Engineering Workflow Management is rated 6.8. The top reviewer of GitLab writes "Powerful, mature, and easy to set up and manage". On the other hand, the top reviewer of IBM Engineering Workflow Management writes "Offers good traceability elements but UI needs improvement ". GitLab is most compared with Microsoft Azure DevOps, Bamboo, SonarQube, AWS CodePipeline and Tekton, whereas IBM Engineering Workflow Management is most compared with Jira, Codebeamer, Microsoft Azure DevOps, Polarion ALM and Endevor.
See our list of best Enterprise Agile Planning Tools vendors.
We monitor all Enterprise Agile Planning Tools 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.
