This article is based on reporting originally published by DevClass and GitLab’s 12.10 release announcement.
GitLab 12.10 Overview
GitLab 12.10 continues the platform’s pattern of shipping significant new capabilities aimed at enterprise and high-tier paying customers, while still including improvements that benefit all subscription levels. The headline addition is requirements management — a feature GitLab is introducing to its platform for the first time — alongside Epic health status tracking, a public incident status page, and a range of security and workflow enhancements.
Requirements Management (Ultimate/Gold)
The most prominent new feature in GitLab 12.10 is the ability to create and view requirements at the project level. This marks the first time GitLab has included requirements management as a native capability, bringing it into direct competition with dedicated requirements tools.
According to principal product manager Farnoosh Seifoddini, GitLab regularly hears from teams about the difficulties of using external requirements management tools — complex integrations, fragmented toolchains, and cumbersome workflows. By incorporating this functionality into its platform, GitLab aims to give teams a single place to manage requirements alongside their code, pipelines, and issues.
In its initial form the feature is basic, but the stated roadmap is to build toward a workflow that can visually demonstrate completeness and compliance — useful for regulated industries and teams that need formal traceability between requirements and delivered code.
Epic Health Status Tracking (Ultimate/Gold)
Ultimate and Gold subscribers can now assign health statuses to individual issues within an Epic. The three available statuses are:
- On track — work is progressing as expected
- Needs attention — something requires a closer look
- At risk — the issue may miss its target or is blocked
Each status is represented with a corresponding colour code in the Epic Tree view. Statuses can also be aggregated into an Epic health report, giving teams and stakeholders an at-a-glance view of where risks are accumulating before they become blockers. This is particularly valuable for programme managers overseeing multiple interconnected workstreams.
Public Incident Status Page (Ultimate/Gold)
When something goes wrong in production, communicating transparently with customers and stakeholders is critical. GitLab 12.10 introduces a public status page feature that allows development and operations teams to push information directly from private incident issues to a public-facing page.
This removes the need for a separate status page service during incidents managed inside GitLab. GitLab has indicated that additional capabilities for other use cases will be added in future releases.
Secure Scanning Improvements
GitLab has improved offline support for its Secure scanning features. Changes include updated scanner job definitions and scanner-specific instructions, along with new workflow documentation. Teams operating in air-gapped or restricted network environments will benefit from these improvements when running security scans without access to the internet.
For online environments, administrators now have access to a new Threat Monitoring page under the Security & Compliance menu. This page provides visibility into total and blocked network traffic and can be used to fine-tune network policies.
Security Enhancements for All Users
Several security improvements in 12.10 are available across all subscription tiers:
- SSH key expiration dates — administrators can now enforce expiry dates on SSH keys, reducing the risk of stale credentials.
- Granular deploy token permissions — more fine-grained control over what deploy tokens can access.
- Global WAF mode — the web application firewall can now be set globally to either logging or blocking mode.
- HashiCorp Vault integration improvements — secrets no longer need to be provided as a plain CI/CD variable. Teams can now authenticate using JSON Web Token (JWT) authentication with HashiCorp Vault, reducing secret exposure in pipeline configurations.
Static Site Editor and New Project Template
GitLab 12.10 adds a new project template that creates a static website pre-configured for GitLab Pages. The template initially supports Middleman as a static site generator and includes a streamlined Static Site Editor, which allows content edits without requiring contributors to understand Git workflows. This is aimed at making GitLab Pages more accessible for documentation sites, project pages, and similar use cases.
Automatic Jira Issue Import
Teams using Jira alongside GitLab can now import Jira issues automatically, eliminating the need for manual data migration or custom integration scripts. This is a meaningful quality-of-life improvement for organisations in the process of consolidating their toolchain into GitLab or that need to maintain synchronisation between both platforms during a transition period.
Release Page Links for Runbooks and Assets
Runbooks and other assets can now be linked directly to the GitLab Release page, giving teams a consolidated view of everything related to a given release — including deployment procedures, rollback guides, and supporting documentation.
AWS Deployment and Autoscaling Improvements (Self-Managed)
Self-managed GitLab installations receive enhancements to simplify deploying to AWS and configuring autoscaling on the platform. Specific details were not elaborated in the release summary, but the improvements are aimed at reducing the operational overhead for teams running GitLab-managed infrastructure on AWS.
Custom Metrics for All Tiers
Custom metrics — previously announced in December 2019 — are now available to all GitLab subscription tiers. This allows teams to define and monitor application-specific metrics within GitLab’s built-in monitoring capabilities, regardless of which subscription plan they are on.
Summary
GitLab 12.10 is a broad release that advances the platform’s ambition to replace multiple point tools across the software development lifecycle. The introduction of requirements management is the most strategically significant addition, positioning GitLab as a potential replacement for dedicated requirements tools in enterprise workflows. Combined with the Epic health tracking, public status pages, and the security improvements available to all tiers, 12.10 is a meaningful step forward for teams running GitLab at scale.