TestOps logo
Try TestOps

GitLab Issues

GitLab Issues is the work-management integration between GitLab and Allure TestOps. It covers:

  • linking test cases and launches to GitLab issues;
  • issue lookup in TestOps by project ID;
  • supported defect workflows that create or reuse GitLab issues;
  • issue-mapping support for automatic links created from test metadata.

This page covers GitLab as an issue tracker. If your goal is result upload or pipeline execution, use GitLab CI instead.

If you have already set up a GitLab CI integration for your GitLab instance, you do not need a new global integration. Add the GitLab project IDs to the existing project integration (see step 3).

Before you begin

  • The GitLab instance URL.
  • Access to create a GitLab personal access token.
  • The GitLab project IDs whose issues TestOps must see.
  • Permission to add or enable integrations in the target TestOps project.

1. Create a GitLab access token

  1. In GitLab, click your avatar and select Preferences.
  2. In the left menu, click Access Tokens.
  3. Click Add new token.
  4. Fill in the fields:
    • Token name — a name to identify the token, for example Token for Allure TestOps.
    • Expiration date — a date within one year from today. After this date the integration will stop working.
  5. Under Select scopes, check api and read_api.
  6. Click Create personal access token.
  7. After the page reloads, copy the token from under Your new personal access token. Save it in a secure location.

You can also use a project access token instead of a personal access token, but it limits the integration to a single GitLab project.

2. Add the global GitLab integration

An instance administrator should:

  1. Open Administration → Integrations in TestOps.
  2. Click + Add integration.
  3. Select GitLab.
  4. Fill in the fields:
    • Name — a stable name for the GitLab instance, for example GitLab production.
    • Endpoint — the URL of the GitLab instance, for example https://gitlab.example.com.
  5. If the GitLab instance uses a self-signed certificate, disable certificate validation.
  6. Click Add integration.

3. Enable GitLab Issues in the project

  1. In TestOps, open the target project.
  2. Go to Settings → Integrations.
  3. Under Available integrations, find the GitLab integration and click Add integration.
  4. Under Settings, add the GitLab project IDs whose issues should be available. To find a project ID, open the project in GitLab and go to Settings → General.
  5. Under Secret, paste the GitLab access token.
  6. Click Test connection and save the project integration.

If a project ID is missing from this list, its issues will not appear in the TestOps issue picker.

If your tests already emit issue labels through an Allure adapter, configure an issue mapping so TestOps can turn those labels into real GitLab issue links automatically.

  1. Open the TestOps project.

  2. Go to Settings → Issues.

  3. Click + Create.

  4. Fill in the fields:

    • Key — the short identifier your tests use in metadata.
    • Issue tracker — the GitLab integration you enabled for the project.

  5. Save the issue mapping.

Once the integration is set up, you can link test cases and launches to GitLab issues manually.

To link a test case:

  1. Go to Test cases and open the test case.
  2. Click the pencil icon next to Issue links.
  3. Click + Add.
  4. Under Issue tracker, select your GitLab Issues integration.
  5. Under Key, select the issue from the list.
  6. Click Submit.

To link a launch:

  1. Go to Launches.
  2. Click ⋯ next to the launch and select Edit.
  3. In the Issues section, click + Add.
  4. Under Issue tracker, select your GitLab Issues integration.
  5. Under Key, select the issue from the list.
  6. Click Submit.

Verify the integration

  1. Open a test case in TestOps and add an issue link.
  2. Confirm that the issue picker can search the expected GitLab issues.
  3. Open a launch and add or edit an issue link there as well.
  4. If your team uses defect export, create or link a defect to confirm that the GitLab issue workflow is available in that view too.

Troubleshooting

The issue picker is empty or missing projects

Check these points first:

  • the GitLab project IDs were added in the project integration settings;
  • the GitLab token can access those projects;
  • the token includes the api and read_api scopes.

The same GitLab integration works for CI but not for issues

The project integration was configured only for pipeline use. Add the issue-tracking project IDs and verify that the token can access them.

© Qameta Software Inc. All rights reserved.