Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

New GitLab integration in Incident Investigation view

We launched the first version of the Incident investigation view in April of 2020 for Bitbucket Pipelines. Shortly after that, we added the ability to investigate deployment-related incidents in Opsgenie from other tools with the creation of our Deployment API.

Today, we're proud to take that flexible approach one step further with the launch of Incident Investigation for GitLab. Now you can investigate your GitLab CI/CD deployments using Opsgenie’s Incident Investigation view, empowering your responders to investigate, identify root cause, and resolve incidents faster.

Let’s walk through how to set it up.

Note: This integration requires you to have GitLab Ultimate because it utilizes group-level web-hooks.

To begin investigating your GitLab CI/CD deployments, connect your GitLab and Opsgenie accounts by selecting the 'Add Connection' button in the GitLab integrations page under global settings.


When you authenticate GitLab you will be able to see the top-level groups from your account that you can connect to your Opssgenie account.


Back in Opsgenie on the Integrations page, all connected groups are listed. Admins can remove GitLab groups connected to Opsgenie, however, new groups can only be added by the GitLab account owner of the groups.


Once the GitLab group is connected to Opsgenie, it’s time to map the GitLab project under the connected GitLab Groups to Opsgenie services.



Next, it’s time to add mappings to each service. You need to manually select each project that you want to map to your services in Opsgenie.



The screenshot below shows that all connected projects listed on the Service settings page.



Now here we are inside the Incident Investigation view. We can see the deployment history for the services in question, and we can click in to get more detail on each deployment and commit. Note that we cannot currently see file changes in this view, but we hope to add that functionality to a future version.


Once the potential cause of an incident has been identified, it is added automatically to the incidents details screen, as shown below.




If you’re using GitLab and Opsgenie together we would love to hear your feedback on the first version of this new connection. Please leave a comment below!

Opsgenie GitLab documentation


Is this only available for the standalone version of Opsgenie? The Jira Service Management integrated Opsgenie does not have the Gitlab settings?

Like # people like this
Sarjeel Syed Yusuf
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 14, 2021

Hey @Gary Blower _Clearvision_ yes it is only available for the standalone version. We are working on introducing it for JSM too. 

@Sarjeel Syed Yusuf  any updates on making this available?

Like Gia Jgarkava likes this

Hi @Sarjeel Syed Yusuf. Are there any updates on adding this feature to JSM?


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events