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

Connecting GitHub and GitLab to the same cloud instance

Anyone running with both the GitHub connector and another Git repository connector like GitLab to populate the development panel?

Wondering if they cause any conflicts with each other. 

1 answer

1 accepted

1 vote
Answer accepted
Andre Dias
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Apr 25, 2023

Hi Majken!


In a nutshell: yes, you can both! Jira has no restriction on how many code tools you have linked to your site or even to a single issue - it's not exclusive to one or the other. If you mention the same issue key in GitHub, Bitbucket, and GitLab, they will all appear in their dedicated section of the development panel. Still, the sum of each category (branches, commits, PRs, builds, deployments) will be displayed in the development panel without specifying how many come from each source. As can be seen in the screenshots below from my test site, I've connected all three of them and two Bitbucket workspaces, and both have a separate section:




This setup won't cause any glitches or errors, the only thing to keep in mind is that having both GitLab and GitHub pointing to the same issue could cause some confusion from a process point of view, but if you're okay with this approach - go for it!

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events