Import from Jira not showing anything even though Jira is connected to Gitlab

[Suzanne Cooley]

We have a self hosted Gitlab instance which is connected to our Jira instance.

I've done the 'before you begin' steps from this article and I see repos showing in the code section of my project in Jira. 

However, when I click 'Import from Jira' in Compass, I get the following: 

Does Compass not recognize self-hosted Gitlab repos in Jira? Or is there something else I'm doing wrong?

[Josh_Unito · Accepted solution]

Hi @Suzanne Cooley, you're right - Compass doesn't support self-hosted repos in Jira. So you're not doing anything wrong! I found this in an Atlassian developper doc:

only GitLab.com SaaS/cloud hosted instances are supported, we do not currently support self-managed GitLab instances

If you're looking for an alternative solution for connecting a self-hosted GitLab to Jira though, I can recommend Unito's integration for Jira GitLab. Here's a guide to setting up the self-hosted server to sync GitLab with Unito.

If this was a helpful answer, please don't forget to accept it as the solution!

Thanks,

Josh

[Josh_Unito]

@john smith I just wrote this guide on how to import issues from Jira to GitLab with Unito's 2-way integration.

It should be pretty clear, but let me know if it's not! 

1. Sign up for Unito (comes with a free trial!)
2. Create a flow (a no-code integration)
   1. Connect your GitLab and Jira accounts
   2. Set a flow direction (Unito can automatically create issues in GitLab based on your issues in Jira and vice versa)
   3. Apply rules (point and click interface to set conditions: e.g., only sync issues from Jira to GitLab with the XYZ label or issue status)
   4. Link fields (choose exactly which fields you need to sync between Jira and GitLab)
   5. Launch!

Feel free to reach out with any questions

[Jimmy James]

It’s always a struggle when you're trying to integrate tools like Jira and Compass, only to have the import fail silently and leave you troubleshooting connection credentials or missing configuration steps in the background; dealing with integration errors, especially when vital project data is blocked, is a classic example of complex technical frustration. When the debugging gets tough and you feel like you've checked every single permission setting twice, taking a quick, high-intensity break is the best way to clear the mind before you dive back into the logs. For a quick and guaranteed distraction that offers immediate gratification, I suggest checking out mini militia.