Connect a team to GitLab.com

Connect a GitLab.com project (read-only) and the test pyramid counts the tests in the test report of its latest finished pipeline. You need current access to the team’s Jira board.

Sign in

Open the Team and admin tools menu (gear) and choose Team settings, or open Test pyramid settings with the sliders button of the Test pyramid section. Then expand GitLab connection. In guided setup the same controls sit under GitLab projects in the Test pyramid step, already open.

Choose Sign in to GitLab, review the permission and authorize the account you intend to use. Finish in the same browser tab. Later the button reads Sign in to GitLab again or Reconnect GitLab (optional).

GitLab grants read_api access to projects and groups available to that account. Choosing a Jira team does not narrow that permission. QA Metrics never asks for your Jira password. GitLab tokens stay in Forge Secret Store and are not shown in Jira.

After returning to Jira, Check GitLab access confirms the account. Reload connection status checks the saved connection without starting another sign-in. The block shows when access expires.

After expiry, Check GitLab access uses the saved connection to renew access without repeating consent. If renewal is already running, reload its status shortly. An unavailable or uncertain renewal requires signing in again.

A team board change always requires a new sign-in. A declined sign-in leaves the previous connection unchanged.

Choose projects

After checking access, choose Load GitLab projects. Available member projects lists projects where the connected GitLab account is a member, twenty at a time. Use More available projects for another page and Select to save a project for this team.

Selected projects survives a page reload; Remove removes only this team’s project choice. A selection is checked against GitLab again when you save it. A conflict requires reloading projects.

Choices are bound to the GitLab account and Jira board. Renewing access or signing in again with the same account keeps them unless you choose Disconnect GitLab. Another account or board must select projects again. Project paths are saved for display; they are not written to logs.

Selecting a project does not turn on background collection; see Automatic report collection. Jira metrics and GitHub pyramid sources keep working independently of GitLab.

Disconnect

Disconnect GitLab blocks use of the team’s connection and cancels its pending sign-in. It removes the team’s project choices, attempts to revoke its renewable GitLab access and deletes its saved credentials.

If cleanup is interrupted, the button reads Retry Disconnect GitLab. Sign-in stays unavailable until cleanup completes. After disconnecting, a new sign-in starts with no selected projects. Jira metrics and GitHub connections are unchanged.

The result distinguishes local cleanup from provider revocation. An unconfirmed provider result means a remote grant may remain. Manage GitLab applications opens GitLab’s own controls. Revoking the whole application there can also disconnect other teams that use the same GitLab account.

Use Cancel pending sign-in to cancel an unfinished first connection. A shared sign-in link, another browser or an expired link cannot complete the flow. Start again from your team in Jira. If a result is uncertain, reload its status first.

Check a selected project’s tests

Choose Check test report beside a selected project. The result, Observed test report · Partial, shows the latest finished pipeline on that project’s default branch and counts for reported, passed, failed, errored, skipped and executed tests.

Failed pipelines can have useful reports. A missing or unreadable report does not fall back to an older successful pipeline. The result is Partial because it describes the test report GitLab makes available to your connected account; it does not prove that every test or downstream pipeline is included.

Missing reports, limits, parsing errors and changing source data have an explicit unavailable result; they are never displayed as zero tests. This check does not save a pyramid observation or start background collection.

Collect a report for the Live pyramid

Choose Collect GitLab report beside a selected project and wait for “GitLab report collection confirmed.” Then select the Test pyramid section title to open Test pyramid details and choose Reload. The saved observation survives page reloads; opening a dashboard never starts a provider scan.

Live combines saved GitHub workflow reports and selected GitLab project observations. GitLab contributes the latest finished pipeline on the default branch and stays Partial. If any selected source has no usable observation, the team shape is unavailable and the source contributions explain the gap.

Failed collection never turns missing data into zero or presents the old observation as a new success. Counts describe reported executions; mirrored projects across providers are not deduplicated.

An expired connection needs Check GitLab access before collecting. Disconnect clears selected projects and their collected reports. Removing and selecting a project again requires a fresh collection. Collected GitLab reports update Live; they are not saved sprint history.

GitLab layers

GitLab reports take one layer for the whole project. In Test sources and layer rules, expand Test layer rules and choose Load layer rules. Each selected GitLab project offers Whole GitLab project is one layer with a layer, or Mixed: leave GitLab tests Unclassified.

GitLab job groups and source-file names are not JUnit archive paths, so the file and suite rules of GitHub do not apply. Changing a whole-project choice reclassifies saved observations on the next Live read; collecting again is unnecessary. Remove saved choice returns the project to Mixed.

Set up reports in the guided tour

In the Test pyramid step, choose GitLab CI on gitlab.com or Both GitHub and GitLab. GitLab sign-in saves your current setup step before leaving Jira; returning to the same browser tab resumes that step without restoring a previous check result.

Select the projects this team uses and choose Collect GitLab report, then Read test reports. Continue: sort your tests lists each GitLab project with its test count: “GitLab reports take one layer for the whole project”. Pick the layer and Save and continue.

You can choose Not now and set up sources later in Team settings.

Automatic report collection

Automatic collection is set in Administration (shown to users with the Administer Jira global permission) under Automatic report collection; choose Load collection schedule first. GitLab collection interval starts Paused; choose Every 6 hours, Every 12 hours or Every 24 hours and Save collection schedule.

The GitLab and GitHub intervals are independent and apply to all teams on the Jira site. After a conflicting or uncertain save, load the schedule again before saving.

GitLab visits up to two selected projects per hour, taking turns across this installation. The interval is a minimum between attempts, not an exact refresh time; larger installations may wait longer. A delayed or lost job never produces a fresh result. Manual collection stays available.

Pausing prevents new automatic collection attempts; an already claimed collection may finish. Removing a project or disconnecting blocks publication of a stale report. When enabled, the collector can renew expired access with the saved connection.

Saved credentials are kept for at most seven days without a successful renewal; reconnect if they are no longer available. Automatic results use the same saved Live observation, counts and Partial qualification as manual collection. Opening the page or a gadget only reads saved observations.