You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Currently I'm trying to figure out how to connect Self-hosted GitLab to Premium Cloud Jira, through different doc articles and blog posts.
So basically, I'd be happy to clarify the following question. This article refers to some kind of "application", which is obviously not the "Gitlab.com for Jira Cloud" app. Could someone please clarify what application it refers to? If it's custom-made - is there any guide on how to implement it?
Curious if you have some tips on this, I was looking thru all the docs today and its not entirely clear from the gitlab side. They reference a couple methods to connect, and specifically state the DVCS needs a direct connection/access to self-hosted.
But looking at the custom app option, if you are creating some manifest file install into Jira, it would be referencing the URL for the self-hosted instance as well. So it seems like either method really needs access into the self-hosted instance.
The gitlab instance I am testing on is in a private network and can go outbound, but has no inbound routes currently. I can add the API token on the gitlab side and manually type an issue ID in and get things to appear on the Jira cloud side, but otherwise not seeing this as entirely useful when strictly working on a private gitlab instance.