2020-10-24 23:57:45 +05:30
---
2022-11-25 23:54:43 +05:30
stage: Manage
2023-07-09 08:55:56 +05:30
group: Import and Integrate
2022-11-25 23:54:43 +05:30
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
2020-10-24 23:57:45 +05:30
---
2023-04-23 21:23:45 +05:30
# Redmine **(FREE)**
2017-08-17 22:00:37 +05:30
2023-05-27 22:25:52 +05:30
You can use [Redmine ](https://www.redmine.org/ ) as an external issue tracker.
2021-04-29 21:17:54 +05:30
To enable the Redmine integration in a project:
2017-08-17 22:00:37 +05:30
2022-10-11 01:57:18 +05:30
1. On the top bar, select **Main menu > Projects** and find your project.
2022-06-21 17:19:12 +05:30
1. On the left sidebar, select **Settings > Integrations** .
2021-04-29 21:17:54 +05:30
1. Select **Redmine** .
1. Select the checkbox under **Enable integration** .
1. Fill in the required fields:
2018-03-27 19:54:05 +05:30
2021-04-29 21:17:54 +05:30
- **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.
<!-- The line below was originally added in January 2018: https://gitlab.com/gitlab - org/gitlab/ - /commit/778b231f3a5dd42ebe195d4719a26bf675093350 -->
**This URL is not used and removal is planned in a future release.**
For more information, see [issue 327503 ](https://gitlab.com/gitlab-org/gitlab/-/issues/327503 ).
2017-08-17 22:00:37 +05:30
2021-04-29 21:17:54 +05:30
1. Select **Save changes** or optionally select **Test settings** .
2017-08-17 22:00:37 +05:30
2021-04-29 21:17:54 +05:30
After you have configured and enabled Redmine, you see the Redmine link on the GitLab project pages,
which takes you to your Redmine project.
2017-08-17 22:00:37 +05:30
2021-04-29 21:17:54 +05:30
For example, this is a configuration for a project named `gitlab-ci` :
2017-08-17 22:00:37 +05:30
2021-04-29 21:17:54 +05:30
- 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`
2019-02-15 15:39:39 +05:30
2021-04-29 21:17:54 +05:30
You can also disable [GitLab internal issue tracking ](../issues/index.md ) in this project.
2023-04-23 21:23:45 +05:30
For more information about the steps and consequences of disabling GitLab issues, see
[Configure project visibility, features, and permissions ](../settings/index.md#configure-project-visibility-features-and-permissions ).
2017-08-17 22:00:37 +05:30
2021-04-29 21:17:54 +05:30
## Reference Redmine issues in GitLab
2017-09-10 17:25:29 +05:30
2021-04-29 21:17:54 +05:30
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.
