Issue Summary

Connecting Jira with an DVCS Organization that contains a very large number of repositories (50000 for example) can fail as Jira has a task that runs hourly to check existing repositories. Given that the DVCS App paginates the request, for 50000 repositories, the application needs to run ~ 500 REST API calls that will return successfully or you risk having some repositories removed. There is no error handling or any handling for rate limitations that might be in place when making such a large request.

Steps to Reproduce

1. Add a DVCS Account with a large number of repositories in an organization.
2. Either trigger rate limiting or slow the connection to cause for a timeout.

Expected Results

You add the organization and Jira allows you link the repositories regardless of the amount of repositories that exist in the org.

Actual Results

While adding repositories, they can simply disappear if during the hourly sync, the operation silently fails. Causing re-work of adding them again, which can again, fail.

Workaround

Only known workaround is to restrict the number of repositories the user connecting to Jira can see. Or move the repositories that will connect with Jira to a smaller organization.