Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Git Integration for Jira and GitLab - Read timed out

Hi everybody,


trying Git Integration for Jira I am having an issue while adding a connection to a GitLab server. When I add the configuration try to connect, it looks promising at first sight:

2020-04-22 09_43_18-Window.png

But afterwards I get the following error message:

2020-04-22 09_32_29-Window.png

Like in one of 50 times it works, but in this way, it's really unusable. Can I workaround it anyhow?

3 answers

Hi Daniel - 

I'm with BigBrassBand - the vendor supporting the Git Integration for Jira app. With GitLab we sometimes see that the API will time out on the initial connection. You can raise the time out setting in the General settings of the Git Integration for Jira app using the Git operations timeout setting

Having said that - if you're seeing this issue this early in the wizard - the issue may be slightly different and may related to the GitLab API taking too long to respond. How many repositories would this GitLab user have access to? You can limit the number of repositories requested from GitLab using the Custom API Path under the Advanced section (visible in the screenshot you shared). 

If you would prefer to continue this privately - contact us at



Hi Adam,

thanks for your quick answer!

I have already tried to increase Git operations timeout setting to 300 ms. It didn't help. I assume you are right about this setting is unrelated to my issue.

The amount of repositories I am trying to index is 1944. I will try to use the suggested limitation option and give you my feedback.




Yes: as supposed, with the limited amount of repositories, the wizard doesn't throw an error. But still, what to do if I want to integrate Jira with all our repositories?

Daniel -

We'll take a look at this to avoid it in the future.

Possible workaround:

Now that you have the integration working with the smaller number of repositories, edit the integration settings and remove the Custom API Path:

Please note that our application clones the repositories locally to Jira. Be sure you have sufficient storage in Jira for this number of repositories.

If that does not work - please reach out to us at and we will look at the specifics (likely ask you for a Jira support zip).



Like Daniel Estermann likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

New cloud apps roundup - June 2021

Since our last roundup in April, Atlassian's Marketplace Partners have added over 100 new cloud apps to the Atlassian Marketplace to help your teams work more efficiently. Let’s take a quick look a...

378 views 5 12
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you