Skip to main content
Setup time: 5 Min
Effortlessly connect GitLab with All Quiet for streamlined incident management.
All changes All Quiet performs in GitLab are shown as actions of the GitLab user who authenticated the integration. We recommend using a dedicated GitLab account (for example All Quiet User) that is not used by a person, so you can clearly distinguish actions from All Quiet vs. actions from your team members.
The first part of this documentation focuses on creating the integration. The second explains how to create GitLab work items based on All Quiet incidents (Outbound). Want to create new incidents from GitLab (Inbound)? Follow the third part of this guideline.

​
Create Outbound Integration

  1. Click on the Outbound Integrations tab.
  2. Click on + Create.
  1. Enter a Display Name for your integration, e.g. “GitLab”.
  2. Select a Team.
    For Organizations with Pro and Enterprise plan: This is going to be the root team of your integration. You will be able to add additional teams in the next step.
  3. Select GitLab as the integration’s type.
  4. Forwarding settings:
    1. Default: Always After Forwarding - GitLab work items will only be created if users manually forward specific incidents or if you set up advanced routing rules for your GitLab integration that automatically forward incidents in specific scenarios.
    2. Alternative: Always will automatically forward all incidents to GitLab and create work items, unless excluded by additional advanced routing rules.
      You can change your selection anytime.
  5. Click Create Outbound Integration.

​
Add All Quiet to your GitLab workspace

Once you’ve successfully created your new outbound integration, you’ll automatically be redirected to its Gitlab Settings page.
  1. Observe that the installation status of the All Quiet integration is still pending.
  2. To complete the integration with GitLab, click on Add to GitLab to authenticate the integration.
In the Edit tab, you can change general settings like the integration’s Forwarding settings.
Only for Pro and Enterprise plan - Manage your Team Connections: The root team is pre-selected, and you can add the integration to further teams within the root team’s organization. Team Administrators can add / remove those teams they are an Administrator in, Organization Administrators & Organization Owners can manage the connections to all teams of the organization.

​
Configure Outbound Integration

If oAuth with GitLab is successful, you are redirected back to your GitLab integration’s details page in All Quiet. Next, you need to configure the integration.Í
  1. As you can see, the Installation Status changed to installed.
  2. Select the GitLab namespace / group / project you want to forward All Quiet incidents to (options depend on your GitLab setup).
  3. Configure how new GitLab work items should be created (for example work item type, Ílabels and default state).
As you can manage the incident in both, All Quiet and GitLab, you can sync the state between both projects. This allows you to manage the incident on one platform only and you don’t have to make changes twice. For changes in All Quiet:
  1. Select the GitLab work item type you want to create for new All Quiet incidents.
  2. Select the initial state for new work items created from All Quiet incidents.
  3. Select the GitLab labels you want to add to new work items created from All Quiet incidents.
  4. Select the GitLab work item state you want to set after resolving an incident in All Quiet.
  5. Select the GitLab work item state you want to set after re-opening an incident in All Quiet.
For changes in GitLab:
  1. Select the GitLab state that sets an incident to Resolved in All Quiet.
  2. Select the GitLab state that sets an incident to Reopened in All Quiet.
Make sure to save your GitLab settings.
If you decide to save & stop here, your GitLab Outbound Integration with All Quiet is ready to go. Depending on your setup, All Quiet incidents will now automatically create work items in GitLab or can be forwarded manually to GitLab. The states will be synced based on your selection.

​
Create All Quiet Incidents From GitLab

This feature is basically the GitLab inbound integration. You can create All Quiet incidents from GitLab work items. Here’s how it works:
If you use both inbound and outbound, avoid creating multiple GitLab inbound integrations that point to the same GitLab project/namespace. Otherwise, an outbound-created work item can trigger another inbound integration and accidentally create duplicate incidents or loops. We recommend using only one inbound integration per GitLab project/namespace.
For Pro and Enterprise plan users: No matter which teams you added in Team Connections when setting up the outbound integration, all All Quiet incidents will always be created in the integration’s root team.
On your GitLab outbound integration’s details page in All Quiet, scroll below section Create Incidents From GitLab To create incidents from GitLab:
  1. Activate Create on new work item and / or Create on work item updateÍ. Otherwise, GitLab work items will not create new All Quiet incidents at all.
    • Enable Create on new work item: All Quiet incidents will be created when creating a GitLab work item matching the criteria below.
    • Enable Create on work item update: All Quiet incidents will be created when updating an existing GitLab work item to match the criteria below.
  2. Optionally, restrict incident creation to GitLab work items that match specific criteria (for example work item type, state or specific labels), depending on your setup.
  3. Save GitLab settings.
You have successfully enabled the GitLab inbound integration. To manage your settings, open your GitLab integration details page.