Stop Jira DVCS connecion scanning all repos in Github

[BBC Application Admin Team]

I can successfully link Jira and our Github org however, there are many repos in the org which Jira then goes to scan. The problem with this is a risk of timeout /github rate limit breach/ unresponsive Jira.

What is the best way to only create a connection between jira and specific repos

[Andy Heinzer]

When using the DVCS to connect Jira to a repo like github, there are steps where you have to create an authorization token.   Please see: Linking a Bitbucket or GitHub repository with Jira

The authorizing account is not necessarily the account that created the key and secret. The authorizing account should have administrative access on all the repositories to be linked. 

So in theory, if you could create a new user account in github, and gave that specific account only admin level access to the specific repos you wanted to sync (not all your repos), you could then use that account when setting up the DVCS in Jira.  This way Jira would only be able to sync repos that specific user account has access to.  I don't believe Jira has any other way to limit this kind of access.  I have to admit, I'm not sure how difficult it would be to create a new user account and grant those admin rights in github, but you can do that, it looks like it's an approach that could work to limit what syncing happens.

[BBC Application Admin Team]

@Andy Heinzerthanks for your suggestion. Sadly, this does not work.

I've created a Github user which owns 2 repos (created via this user) and is added as a admin on 3 other repos (owned by someone else).

Jira DVCS account information will only show the 2 repos owned by that user, not the ones its an admin for.

[Andy Heinzer]

Which account created the key and secret?

And which account is the authorizing account?

These are not necessarily going to be the same account in all cases.  In your case, I believe that the key and secret could be created by the owner, but the authorizing account would be the other admin account here.  In this setup, this should work to allow Jira to sync only the repos that admin account has access to and not other repos that authorizing account does not have access to.

I would recommend trying to remove the current DVCS settings and try to set this up as such again. If you find this is not the expected behavior here, please let me know.  It might be better to create a support request where we can gather some potentially more sensitive data from your in a private channel to better understand what is happening here.

Andy