

JIRA Portfolio and GitLab compete in the project management and DevOps tools category. JIRA Portfolio appears to have the upper hand in agile project management and visualization, while GitLab shines in CI/CD capabilities.
Features: JIRA Portfolio offers a centralized database for project management, diverse workflow configurations, and integration with other JIRA products. It also includes agile visualization tools. GitLab stands out with its CI/CD capabilities, repository management, and integration with cloud services, simplifying deployment and collaboration.
Room for Improvement: JIRA Portfolio needs better reporting flexibility, UI clarity, and broader platform integrations. Users also find project-level visibility and navigation challenging. GitLab could enhance AWS integration, security features, and support services. Its CI features could be more comprehensive, and more high-level metrics would aid non-developer stakeholders.
Ease of Deployment and Customer Service: JIRA Portfolio supports both on-premises and cloud deployments with generally positive technical support, though accessing customer service can be challenging. GitLab offers similar deployment options but experiences integration issues with third-party tools. Users value the support but note room for improvement in response times and accessibility.
Pricing and ROI: JIRA Portfolio’s tiered pricing can be expensive for smaller teams, yet it offers quick ROI by enhancing project management efficiency. GitLab is costlier for small teams but includes a free tier and open-source options, balancing cost with advanced capabilities for a good value.
Migrating to GitLab is bringing time-saving benefits, and everything is easier to automate.
We have saved time significantly, reducing deployment time from four hours to five minutes per deployment.
In terms of operational efficiency, a ten to twenty percent increase in speed could quite easily be seen from using the Issues and Epics tracking feature.
The tool provides tracking for projects and activities, with detailed insights into which team members worked on activities and the time invested in each task.
We have rarely needed to escalate issues to technical support since GitLab usually runs seamlessly.
I have interacted with architects for some advice during the implementation, and they were prompt in their response.
I have had meetings where they taught me, explained things, and provided guidance for starting from scratch.
The support was good with no challenges.
We are satisfied with the support from our provider.
It has all the features required for our coding and deployment needs, which makes it scalable to our changing requirements.
We're transitioning to OpenShift for future scalability with increased user numbers.
For scaling, other deployment options from GitLab's side need to be adopted.
In terms of scalability, I would give JIRA Portfolio a ten out of ten.
I have not encountered any performance or stability issues with GitLab so far.
The updates are frequent and demanding, happening at least once a week due to security reasons.
We raised a request with GitLab support, but they were unable to help because they could not find the root cause of what went wrong.
In comparison to Planisware, it is very stable.
It would be beneficial to have a user-friendly interface for setting up these configurations, instead of just writing YAML files.
It is essential to conduct proper testing, such as unit tests and code coverage, within the SDLC pipelines.
GitLab can improve its user interface to make conflict resolution more user-friendly.
Making the report creation process faster and easier with drag-and-drop features would be beneficial.
The setup process for JIRA Portfolio is complex.
Even when working in other small organizations, we opted for GitLab as it was cost-efficient.
The pricing of GitLab is reasonable, aligning with what I consider to be average compared to competitors.
The price is high, and it limits user accessibility.
It is not considered expensive in the market.
As we implement automated testing and DevSecOps, it speeds up the process by forty to sixty percent.
The Ultimate version offers enhanced features for security scanning through DAST and SAST analysis, which have greatly benefitted our project workflow.
By integrating GitLab as a DevOps platform, we have enhanced agility, improved our time to market, and different teams can work collaboratively on various projects.
The reporting feature is comprehensive and easy to use, which aids in planning and forecasting.
The cloud accessibility and quick task creation capabilities make collaborating with the tool a great feature for working with my team.
| Product | Mindshare (%) |
|---|---|
| GitLab | 28.5% |
| JIRA Portfolio | 1.4% |
| Other | 70.1% |


| Company Size | Count |
|---|---|
| Small Business | 37 |
| Midsize Enterprise | 11 |
| Large Enterprise | 46 |
| Company Size | Count |
|---|---|
| Small Business | 15 |
| Midsize Enterprise | 12 |
| Large Enterprise | 32 |
GitLab offers a secure and user-friendly platform for CI/CD pipeline management, code repository control, and collaboration, enhancing development speed and efficiency. It facilitates automation with extensive customization and tool integration, ideal for DevOps processes.
GitLab supports source code management, version control, and collaborative development. It's frequently used in CI/CD processes to automate builds and deployments while integrating DevOps practices. GitLab allows companies to manage repositories, automate pipelines, conduct code reviews, and maintain development lifecycles. The platform supports infrastructure and configuration management, enabling efficient code collaboration, deployment automation, and comprehensive repository handling. Many organizations commit and deploy developed code using GitLab's capabilities.
What are GitLab's most valuable features?In specific industries, GitLab serves as a backbone for source code management and CI/CD implementation. Companies leverage its capabilities for infrastructure management and deployment automation, thus streamlining project delivery timelines. Its ability to handle configuration management and code repositories effectively aids in maintaining development lifecycles, making it a preferred choice for organizations committed to enhancing their DevOps practices.
JIRA Portfolio offers centralized data access, collaboration, and agile alignment through customizable workflows and robust integration, making it vital for project and portfolio management.
JIRA Portfolio is designed to enhance project management with centralized data and ease of collaboration for agile teams. It provides customizable workflows and comprehensive reporting with integration capabilities. Its user-friendly interface supports visualization, task management, and dependency tracking through powerful dashboards. It is flexible and scalable, adapting to specific needs and promoting effective communication across teams. Stability and familiarity make it popular for managing projects on cloud and on-premises, supporting Scrum and Kanban methodologies.
What are the most valuable features of JIRA Portfolio?Organizations in industries such as software development use JIRA Portfolio for issue tracking, project management, and agile planning. It aids in task management, creating roadmaps, and resource allocation, providing insights through dashboards. It supports both cloud and on-premises deployments, benefiting scrum and kanban practices.
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.