Redmine

You can use Redmine as an external issue tracker. To enable the Redmine integration in a project:

  1. On the left sidebar, select Search or go to and find your project.
  2. Select Settings > Integrations.
  3. Select Redmine.
  4. Under Enable integration, select the Active checkbox.

  5. Fill in the required fields:

    • Project URL: The URL to the Redmine project to link to this GitLab project.
    • Issue URL: The URL to the Redmine project issue to link to this GitLab project. The URL must contain :id. GitLab replaces this ID with the issue number.
    • New issue URL: The URL to use to create a new issue in the Redmine project linked to this GitLab project. This URL is not used and removal is planned in a future release. For more information, see issue 327503.
  6. Optional. Select Test settings.
  7. Select Save changes.

After you have configured and enabled Redmine, you see the Redmine link on the GitLab project pages, which takes you to your Redmine project.

For example, this is a configuration for a project named gitlab-ci:

  • Project URL: https://redmine.example.com/projects/gitlab-ci
  • Issue URL: https://redmine.example.com/issues/:id
  • New issue URL: https://redmine.example.com/projects/gitlab-ci/issues/new

You can also disable GitLab internal issue tracking in this project. For more information about the steps and consequences of disabling GitLab issues, see Configure project visibility, features, and permissions.

Reference Redmine issues in GitLab

You can reference your Redmine issues using:

  • #<ID>, where <ID> is a number (example #143).
  • <PROJECT>-<ID>, for example API_32-143, where:
    • <PROJECT> starts with a capital letter, followed by capital letters, numbers, or underscores.
    • <ID> is a number.

In links, the <PROJECT> part is ignored, and they always point to the address specified in Issue URL.

We suggest using the longer format (<PROJECT>-<ID>) if you have both internal and external issue trackers enabled. If you use the shorter format, and an issue with the same ID exists in the internal issue tracker, the internal issue is linked.