"The most valuable features of Gitlab are integration with CIE and the ability to rapidly deploy solutions, projects, and applications. It is very easy to use, and there are no complaints."
"GitLab offers a good interface for doing code reviews between two colleagues."
"Everything is easy to configure and easy to work with."
"It is very useful for reviews. We are using branch merging operations and full reset operations. It is also very useful for merging our code and tracking another branch. The graph diagrams of Git are very useful. Its interface is straightforward and not too complex for us."
"The best thing is that as the developers work on separate tasks, all of the code goes there and the other team members don't have to wait on each other to finish."
"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."
"It speeds up our development, it's faster, safer, and more convenient."
"I like that it's easy to deploy our services over GitLab. The customer support is also good with a really active community. You have a lot of support that you can get online with your stack. That is probably one of the benefits of using GitLab. It's also really fast."
"The most valuable features are the ability to customize the entries and to update them quickly. Since the new version they released, we started utilizing the customization features to create specific codes and symbols for our teams that were not available before. For example, in team A each person had their own symbols and we had our own demarcation. When our project or task was completed, we had a code that we could enter online that let the main project managers know that it was time to remove it."
"Some of the most valuable features are the configurations and dashboards."
"Velocity and reporting provide good visibility, burndown charts, and particularly velocity measurement."
"Jira Align helps us manage communication and tasks for a variety of teams without overlap."
"The most valuable feature is that engineers can access the Jira database and just search for the tasks that are assigned to them. They can then update the status on their own in those records that are assigned to them."
"In the free version, when a merge request is raised, there is no way to enforce certain rules. We can't enforce that this merge request must be reviewed or approved by two or three people in the team before it is pushed to the master branch. That's why we are exploring using some agents."
"Based on what I know so far, its integration with Kubernetes is not so good. We have to develop many things to make it work. We have to acquire third-party components to work with Kubernetes."
"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."
"It should be used by a larger number of people. They should raise awareness."
"The only thing our company is really waiting on in terms of features is the development of metrics."
"The solution could improve by providing more integration into the CI/CD pipeline, an autocomplete search tool, and more supporting documentation."
"We would like to generate document pages from the sources."
"The documentation could be improved to help newcomers better understand things like creating new branches."
"One of the biggest issues I found in the new version was once we clicked on one of the tasks that were specifically for our group and went to look at the other portfolios in other areas we had to browse all the way back to the beginning. If you click the back button, it would not work, it stayed the same place. Additionally, if you click on page B, but then you wanted to go back to page A it would not go back to page A. You would have to browse back to the portfolio and then find your group again and open it. This was the only issue that I had with it and I am not sure if it is a Jira issue or it was because of the way the site was laid out."
"Deployment was very complex."
"Lacks sufficient reporting capabilities."
"The workflows are scalable from portfolio to individual level but can sometimes be complex to navigate."
"There is no linkage between the Jira records and the overarching schedule. We maintain the overarching schedule in Microsoft Project, and there is no linkage back and forth with the Jira tasks. They are independent of each other."
GitLab is ranked 4th in Enterprise Agile Planning Tools with 16 reviews while Jira Align is ranked 7th in Enterprise Agile Planning Tools with 5 reviews. GitLab is rated 8.2, while Jira Align is rated 7.8. The top reviewer of GitLab writes "Provides or mandates quantitative code into the Master". On the other hand, the top reviewer of Jira Align writes "An easy learning curve with great integrations; reporting provides good visibility". GitLab is most compared with Microsoft Azure DevOps, TeamCity, Tekton, Sonatype Nexus Lifecycle and GoCD, whereas Jira Align is most compared with Planview LeanKit, Microsoft Azure DevOps, ServiceNow IT Business Management, Targetprocess and ServiceNow DevOps. See our GitLab vs. Jira Align report.
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.
