GitLab vs JIRA Portfolio comparison

Cancel
You must select at least 2 products to compare!
GitLab Logo
14,492 views|11,537 comparisons
98% willing to recommend
Atlassian Logo
1,029 views|826 comparisons
98% willing to recommend
Comparison Buyer's Guide
Executive Summary

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.
To learn more, read our detailed GitLab vs. JIRA Portfolio Report (Updated: May 2024).
772,649 professionals have used our research since 2012.
Featured Review
Quotes From Members
We asked business professionals to review the solutions they use.
Here are some excerpts of what they said:
Pros
"We're only using the basic features of GitLab and haven't used any advanced features. The solution works fine, so that's what we like about GitLab. We're party using GitHub and GitLab. We have a GitHub server, while we use GitLab locally or only within our team, and it works okay. We don't have any significant problems with the solution. We also found the straightforward setup, stability, and scalability of GitLab valuable.""The important feature is the entire process of versioning source code maintenance and easy deployment. It is a necessity for the CI/CD pipeline.""The SaaS setup is impressive, and it has DAST solutioning.""As a developer, this solution is useful as a repository holder because most of the POC projects that we have are on GitLab.""Everything is easy to configure and easy to work with.""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 convenience. I am able to trace back most of my changes up to a far distance in time and it helps me to analyze and see the older version of the code.""I like that you can use GitLab as a double-sided solution for both DevOps and version management. It's a good product for working in these two areas, and the user interface makes it easy to understand."

More GitLab Pros →

"The most valuable features of the JIRA Portfolio are the ease of use, many developers are familiar with it.""The solution is very stable.""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.""Managing product development and managing inter-team communications are also valuable features.""The integration is very good. We've more or less integrated with everything including reporting and registering.""The workflow and bucket features are most helpful.""The solution is stable and reliable.""With JIRA, you can do amazing things by developing connectors, embedding features, and adding new fields to create new things."

More JIRA Portfolio Pros →

Cons
"I've noticed an area for improvement in GitLab, particularly needing to go through many steps to push the code to the repository. Resolving that issue would make the product better. My team quickly fixed it by writing a small script, then double-clicking or enabling the script to take care of the issue. However, that quick fix was from my team and not the GitLab team, so in the next release, if an automatic deployment feature would be available in GitLab, then that would be good because, in Visual Studio, you can do that with just one click of a button.""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.""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 integration and storage capabilities could be better.""GitLab could consider introducing a code-scanning tool. Purchasing such tools from external markets can incur charges, which might not be favorable. Integrating these features into GitLab would streamline the pipeline and make it more convenient for users.""The tool should include a feature that helps to edit the code directly.""Merge conflicts and repository maintenance could improve. If there is someone new to the system they would not know if there is a conflict.""Atlassian offers more products than GitLab. GitLab offers source control management, version control and collaboration between developers. Atlassian offers features on top of this as well as more integration points for developers."

More GitLab Cons →

"This solution is not able to be integrated with other solutions because you have to upgrade it and pay for more licensing.""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.""We are using the on-premise deployment, but it is slower and not as easy to manage as the cloud version.""Converting a task into an epic is very troublesome.""When using a scrum board, it only shows the current or open sprint. However, we also need to see past and future sprints, which is important for planning the next sprint. To solve this, we tried using a Kanban board instead, but since we follow the Scrum methodology, it's not the ideal solution.""The HR aspect of the solution could be improved.""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.""It would be nice if it could provide an end-to-end solution for a project."

More JIRA Portfolio Cons →

Pricing and Cost Advice
  • "I think that we pay approximately $100 USD per month."
  • "The price is okay."
  • "It seems reasonable. Our IT team manages the licenses."
  • "Its price is fine. It is on the cheaper side and not expensive. You have to pay additionally for GitLab CI/CD minutes. Initially, we used the free version. When we ran out of GitLab minutes, we migrated to the paid version."
  • "It is very expensive. We can't bear it now, and we have to find another solution. We have a yearly subscription in which we can increase the number of licenses, but we have to pay at the end of the year."
  • "I don't mind the price because I use the free version."
  • "We are using its free version, and we are evaluating its Premium version. Its Ultimate version is very expensive."
  • "The price of GitLab could be better, it is expensive."
  • More GitLab Pricing and Cost Advice →

  • "This solution has a comparable pricing in comparison to other similar products on the market."
  • "The pricing of the solution is expensive."
  • "We only have nine people using it so we have a standard cost of $150 dollar per year. There are only additional costs if you exceed the limit of users, then you start paying by user. The cost is significantly higher."
  • "The pricing continues to get higher."
  • "The product is really not very expensive."
  • "We pay our fees annually, although monthly payments are also available."
  • "The price could be improved."
  • "We have a license to use JIRA Portfolio, we are not using the free version."
  • More JIRA Portfolio Pricing and Cost Advice →

    report
    Use our free recommendation engine to learn which Enterprise Agile Planning Tools solutions are best for your needs.
    772,649 professionals have used our research since 2012.
    Questions from the Community
    Top Answer: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.
    Top Answer:For small-scale usage, GitLab offers a free tier. For enterprise pricing, GitLab is more expensive than GitHub, as it's not as widely adopted. GitLab is the preferred choice for many developers… more »
    Top Answer:I believe there's room for improvement in the advanced features, particularly in enhancing the pipeline functionalities. Better integration and usability within the pipeline could make a significant… more »
    Top Answer:The solution's tracking capabilities helped ensure we had full visibility into planned work and scheduled work.
    Top Answer:I do not believe that the product provides value for money since I feel that it is quite expensive. I don't have a clear view of the cost associated with the licensing part of the tool. The product… more »
    Top Answer:From an improvement perspective, I would like to see the product of more integration capabilities with different platforms. The APIs work, but what my company noticed is that Atlassian offers… more »
    Ranking
    Views
    14,492
    Comparisons
    11,537
    Reviews
    50
    Average Words per Review
    406
    Rating
    8.6
    Views
    1,029
    Comparisons
    826
    Reviews
    27
    Average Words per Review
    488
    Rating
    8.3
    Comparisons
    Also Known As
    Fuzzit
    Portfolio for JIRA
    Learn More
    Overview

    GitLab is a complete DevOps platform that enables teams to collaborate and deliver software faster. 

    It provides a single application for the entire DevOps lifecycle, from planning and development to testing, deployment, and monitoring. 

    With GitLab, teams can streamline their workflows, automate processes, and improve productivity.

    Jira Portfolio is an agile roadmapping tool designed to help teams build plans, envision the big picture, track progress, and share the process with stakeholders.

    Jira Portfolio is planned based. A plan in Portfolio is a complete view of the tasks, teams, and release dates for your Jira projects.

    Once you start to create a plan, there are three main factors you need to define: 

    • Scope: A list of tasks that need to be carried out in order to complete the plan.
    • Teams: Who will be implementing the work? With the correct data in place, Portfolio can estimate how long it will take for the team to complete their tasks.
    • Releases: Your scheduled release date.

    With Jira Portfolio, you can create a visual timeline to gain visibility across each of your teams and projects in a single place from a granular level and review cross-team and cross-project dependencies to prevent bottlenecks. This visibility can help you plan realistic release dates and manage your team’s capacity. The solution allows you to try out different scenarios with your roadmap and resources to help guide your decision making. Once you have a solid plan, you can easily integrate with Jira Software and commit your changes.

    Jira Portfolio allows managers to easily add team members. The tool’s powerful scheduling algorithm assigns tasks to teams while taking priorities and dependencies into account so it can create a realistic forecast for project completion. 

    Jira Portfolio Benefits

    Some of the top benefits of using Jira Portfolio include:

    • Roadmaps and roadmaps dependencies: Roadmaps list details about the tasks that need to be executed in order to complete a project, as well as predictions for when they will be completed, which teams are in charge of the task, and a list of resources they require. By setting dependencies on your team’s roadmaps, unnecessary bottlenecks are avoided.  
    • Integration with Jira: Jira Portfolio is dynamically integrated with your Jira Software project data and constantly pulls your latest data from Jira Software, allowing you to plan your projects with updated information.
    • Envision scenarios: Create what-if scenarios and save them to Jira if you decide to adopt them.
    • Reporting: Share capacity reports and more to allow team members and stakeholders to gain visibility and insights into the process.
    • Task completion estimation methods: Estimate how long a specific task will take and compare these estimations with the actual time to completion to help assess team performance and efficiency and improve the accuracy of estimation calculations over time. 

    Reviews from Real Users

    Jira Portfolio stands out among its competitors for a number of reasons. Two major ones are its roadmap creation tools and its flexibility.

    Meeta L., a lead product manager at a tech vendor, says, “The valuable features of the JIRA Portfolio are the customization it provides which is very useful and the Agile project management capability.”

    Juan P., a senior IT project manager at Avantica, writes, “Portfolio helps us increase the visibility of projects' status and management with remote workers who make up most of the company.”

    Sample Customers
    1. NASA  2. IBM  3. Sony  4. Alibaba  5. CERN  6. Siemens  7. Volkswagen  8. ING  9. Ticketmaster  10. SpaceX  11. Adobe  12. Intuit  13. Autodesk  14. Rakuten  15. Unity Technologies  16. Pandora  17. Electronic Arts  18. Nordstrom  19. Verizon  20. Comcast  21. Philips  22. Deutsche Telekom  23. Orange  24. Fujitsu  25. Ericsson  26. Nokia  27. General Electric  28. Cisco  29. Accenture  30. Deloitte  31. PwC  32. KPMG
    Rosetta Stone, Sprint, UBS, Workday, Expedia, J.P. Morgan
    Top Industries
    REVIEWERS
    Financial Services Firm16%
    Computer Software Company16%
    Manufacturing Company13%
    Retailer10%
    VISITORS READING REVIEWS
    Educational Organization25%
    Computer Software Company12%
    Financial Services Firm11%
    Manufacturing Company8%
    REVIEWERS
    Computer Software Company34%
    Manufacturing Company14%
    Educational Organization10%
    Financial Services Firm7%
    VISITORS READING REVIEWS
    Financial Services Firm20%
    Computer Software Company16%
    Manufacturing Company10%
    Government7%
    Company Size
    REVIEWERS
    Small Business44%
    Midsize Enterprise9%
    Large Enterprise47%
    VISITORS READING REVIEWS
    Small Business15%
    Midsize Enterprise34%
    Large Enterprise51%
    REVIEWERS
    Small Business26%
    Midsize Enterprise20%
    Large Enterprise54%
    VISITORS READING REVIEWS
    Small Business16%
    Midsize Enterprise11%
    Large Enterprise74%
    Buyer's Guide
    GitLab vs. JIRA Portfolio
    May 2024
    Find out what your peers are saying about GitLab vs. JIRA Portfolio and other solutions. Updated: May 2024.
    772,649 professionals have used our research since 2012.

    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.