2020-10-24 23:57:45 +05:30
---
2022-11-25 23:54:43 +05:30
stage: Manage
2021-10-27 15:23:28 +05:30
group: Integrations
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
# Bugzilla **(FREE)**
2017-08-17 22:00:37 +05:30
2021-06-08 01:23:25 +05:30
[Bugzilla ](https://www.bugzilla.org/ ) is a web-based general-purpose bug tracking system and testing
tool.
2017-08-17 22:00:37 +05:30
2021-06-08 01:23:25 +05:30
You can configure Bugzilla as an
[external issue tracker ](../../../integration/external-issue-tracker.md ) in GitLab.
2017-08-17 22:00:37 +05:30
2021-06-08 01:23:25 +05:30
To enable the Bugzilla 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-06-08 01:23:25 +05:30
1. Select **Bugzilla** .
1. Select the checkbox under **Enable integration** .
1. Fill in the required fields:
2017-08-17 22:00:37 +05:30
2021-06-08 01:23:25 +05:30
- **Project URL**: The URL to the project in Bugzilla.
For example, for a product named "Fire Tanuki":
`https://bugzilla.example.org/describecomponents.cgi?product=Fire+Tanuki` .
- **Issue URL**: The URL to view an issue in the Bugzilla project.
The URL must contain `:id` . GitLab replaces `:id` with the issue number (for example,
`https://bugzilla.example.org/show_bug.cgi?id=:id` , which becomes
`https://bugzilla.example.org/show_bug.cgi?id=123` ).
- **New issue URL**: The URL to create a new issue in the linked Bugzilla project.
For example, for a project named "My Cool App":
`https://bugzilla.example.org/enter_bug.cgi#h=dupes%7CMy+Cool+App` .
2019-02-15 15:39:39 +05:30
2021-06-08 01:23:25 +05:30
1. Select **Save changes** or optionally select **Test settings** .
2017-08-17 22:00:37 +05:30
2021-06-08 01:23:25 +05:30
After you configure and enable Bugzilla, a link appears on the GitLab
project pages. This link takes you to the appropriate Bugzilla project.
2017-09-10 17:25:29 +05:30
2021-06-08 01:23:25 +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 ).
2021-06-08 01:23:25 +05:30
## Reference Bugzilla issues in GitLab
You can reference issues in Bugzilla using:
- `#<ID>` , where `<ID>` is a number (for 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.
The `<PROJECT>` part is ignored in links, which 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.
2020-03-13 15:44:24 +05:30
## Troubleshooting
2022-07-16 23:28:13 +05:30
To see recent service hook deliveries, check [service hook logs ](index.md#troubleshooting-integrations ).
