matthew.david could you check if your issue is related to DCON-419? If not, could you raise a support ticket at https://support.atlassian.com? That would help us gather more info and proceed to troubleshoot and help you fix the issue.

I'm still having issues with DVCS w/ GitHub not seeing private organizational repos. I'm using a non-OnDemand (and not publicly accessible, so the OAuth trick doesn't work) instance of JIRA with a personal account that is attached to an organization and I cannot see any of the organization's private repos. I'm running JIRA v6.2.5. Any ideas?

Just for the record, it turns out that Matt's problem was DCON-419. Following the workaround fixed the problem.

It's my personal account on standard GitHub, which is an owner of the organization and has full access to all the repositories. I've opened a support ticket (problem-report-105427), but they seem to have mischaracterized the issue as another one (DCON-393/DCON-448) which is not consistent with the behavior I'm seeing (and still see with the recent 2.1.21 DVCS release). I've never been able to see any repositories, where those reports seem to say that re-adding the organizations will make things work again.

Hi mdavis3,

If you click on the cog to the far right of the Organization name on the DVCS Accounts page, and select "Reset OAuth Settings", what account do you see on the dialog? Double check that the account mentioned on the dialog has access to the private repositories in the organization.

Is this GitHub Enterprise or GitHub?

If the problem persists, please raise a support ticket.

Cheers,
Zehua Liu

Charles Portwood's suggested workaround for hooking up private organization-owned GitHub repos seems to be broken again as of DVCS connector version 2.1.20 and 2.1.21... Linking an account always shows "No repositories", regardless if you've hacked the org into the return URL on the auth page or set it up from the UI, canceled, and regen'd the OAuth token. Has anyone else been able to get this to work lately? I'm doing it with a Github organization owner account that can see all repos in the org, and I've tried it with both personal- and organization-owned OAuth tokens.

Hi rpei1,

You can't update DVCS Connector on OnDemand, there is always the latest version installed. If it is not so, contact support, please.

Cheers,
Miroslav Stencel | Atlassian

I cannot get that update to work. I am using the tool to update Add-ons by URL, and get this error:

The add-on at https://marketplace.atlassian.com/download/plugins/com.atlassian.jira.plugins.jira-bitbucket-connector-plugin cannot be installed on this OnDemand instance.

Should OnDemand allow me to update this plugin via file upload? Because I'm not seeing that option for me.

This looks like a problem with the way the version history has been ordered in the Marketplace. I've raised a bug for it under AMKT-8432 and the workaround to add the new version is:

1. Download the version from https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-bitbucket-connector-plugin/versions
2. Upload the add-on in the Manage add-ons section of the Add-on Manager.

Cheers,
David Currie
Atlassian Support

Same here – how can we update the plugin? 6.1.3 comes with 1.4.2.x, no updates available..