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 valuable feature of GitLab is the automatic merging of code."
"I find the features and version control history to be most valuable for our development workflow. These aspects provide us with a clear view of changes and help us manage requests efficiently."
"A user friendly solution."
"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."
"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."
"It speeds up our development, it's faster, safer, and more convenient."
"GitLab offers a good interface for doing code reviews between two colleagues."
"It is very flexible and easy because you can store data on cloud."
"The most valuable features of Jira are the dashboards where we see all the features lined up with the release dates in the portfolio view, it is very good."
"Has many functionalities including good supervision and workflows."
"The product's integration capabilities work pretty well, especially considering that more tools are always needed in enterprise-sized businesses."
"Its stability is very reliable."
"The solution includes good and fast notifications for other project team members."
"The feature that we like the most is that JIRA enables modules. Atlassian provides a lot of products around JIRA, such as compliance for the documentation, BitBucket for the Git version. We are new to these products developed by Atlassian, but they can integrate very easily. Generally, when an editor is developing a solution, they think about integrating with JIRA. When we are looking for any other solution, they plan to easily integrate with JIRA."
"In general, the valuable features of the tool are its capabilities concerning dependency reports and task status."
"The product's centralized database creates a single source of data for working groups so no data needs to be reconciled."
"As a partner, sometimes it's difficult to get support. They have a really complicated procedure for their support."
"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."
"The documentation could be improved to help newcomers better understand things like creating new branches."
"The price of GitLab could improve, it is high."
"Merge conflicts and repository maintenance could improve. If there is someone new to the system they would not know if there is a conflict."
"GitLab would be improved with the addition of templates for deployment on local PCs."
"GitLab can improve the integration with third-party applications. It could be made easier. Additionally, having API control from my application could be helpful."
"Perhaps the integration could be better."
"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."
"As there are no perfect solutions and considering that I rate JIRA Portfolio's stability an eight out of ten, I feel it is an area with certain shortcomings where improvements are required."
"When I want to embed Jira Portfolio in a complete HLI cycle, I'm missing things to evaluate my ethic into my value stream."
"The product's initial setup phase is complex."
"An improvement would be if Portfolio were integrated with Office 365."
"The workflow needs improvement."
"The team-centric view is slightly weaker in JIRA compared to its competitors, especially considering how I can evaluate how each resource has been placed, not just in one project but across JIRA."
"The product could do with more flexible reporting."
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.
