We performed a comparison between GitLab and JIRA Portfolio based on real PeerSpot user reviews.
Find out in this report how the two Enterprise Agile Planning Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The most important features of GitLab for us are issue management and all the CI/CD tools. Another aspect that I love about GitLab is the UI."
"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."
"We have seen a couple of merge requests or pull requests raised in GitLab. I see the interface, the way it shows the difference between the two source codes, that it is easy for anyone to do the review and then accept the request; the pull request is the valuable feature."
"A user friendly solution."
"The most valuable feature of GitLab is the ability to upload scripts and make changes when needed and then reupload them. Additionally, the solution is user-friendly."
"The most valuable features of GitLab are the CI/CD pipeline and code management."
"The solution is stable."
"It scales well."
"The solution is stable and reliable."
"The most valuable feature is the dashboard where we can see all of our projects and apply filters to shortlist those projects."
"It is a good scalable solution that I have used for small projects and reasonably large projects."
"The best features of JIRA are its flexibility and configurability, allowing us to tailor it to our specific needs."
"The dashboard is the most valuable feature. The user experience is very good, it's easy to use."
"The integration is very good. We've more or less integrated with everything including reporting and registering."
"I think the solution's most important and valuable feature is its ability to track the issues."
"Has many functionalities including good supervision and workflows."
"GitLab's UI could be improved."
"We would like to have easier tutorials. Their tutorials are too technical for a user to understand. They should be more detailed but less technical."
"The documentation could be improved to help newcomers better understand things like creating new branches."
"I would like configuration of a YML file to be done via UI rather than a code file."
"The solution could improve by providing more integration into the CI/CD pipeline, an autocomplete search tool, and more supporting documentation."
"GitLab could improve the patch repository. It does not have support for Conan patch version regions. Additionally, better support for Kubernetes deployment is needed as part of the package."
"As a partner, sometimes it's difficult to get support. They have a really complicated procedure for their support."
"This solution could be improved by adding modifications such as slack notifications."
"The query features should improve in JIRA Portfolio. For example, if I would have to create my own queries for looking into something such as what business features we have released last month, or the last three months, I don't know if I can do it. The solution requires a certain level of expertise."
"The interface JIRA Portfolio could improve."
"JIRA Portfolio could improve new implementation because if I want integration for the complete wide frame tools it cannot provide any wide frame tools."
"This solution is not able to be integrated with other solutions because you have to upgrade it and pay for more licensing."
"The solution's look and feel could be a bit more intuitive and user friendly."
"Jira has room for improvement in terms of managing various projects and linking requirements centrally under one project. They could include some add-ons that enable you to link all the requirements and put them into a centralized place. That central place should be restricted to a limited set of users with privileges based on user groups with those rights."
"Converting a task into an epic is very troublesome."
"n the next version I would like to see better reporting and safer plugins, as well as easier scalability."
GitLab is ranked 2nd in Enterprise Agile Planning Tools with 70 reviews while JIRA Portfolio is ranked 4th in Enterprise Agile Planning Tools with 55 reviews. GitLab is rated 8.6, while JIRA Portfolio is rated 8.2. The top reviewer of GitLab writes "Powerful, mature, and easy to set up and manage". On the other hand, the top reviewer of JIRA Portfolio writes "Powerful, flexible solution with a bit of a learning curve". GitLab is most compared with Microsoft Azure DevOps, SonarQube, Bamboo, AWS CodePipeline and Tekton, whereas JIRA Portfolio is most compared with Jira Align, Oracle Primavera Portfolio Management, Microsoft Azure DevOps, Microsoft Project Server and Microsoft Project. See our GitLab vs. JIRA Portfolio 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.
