felix.sargent from a quick look, none of the repositories on the DVCS Accounts page are linked, which means that the commits and PRs in those repositories will not be synchronized into JIRA. If you want any of those commits or PRs to be associated with the JIRA issues, you should link the corresponding repositories (by clicking on the checkbox to the left of the repository).

If the problem still persists, please create a support ticket at https://support.atlassian.com/browse/JST. Our support engineers would be able to respond to your requests much more quickly.

I'm still having issues on account Repose.atlassian.net getting to github rackerlabs.
Could anyone help out?
DVCS is at 2.1.4

Version:
2.1.4
Developer:
Atlassian
Add-on key:
com.atlassian.jira.plugins.jira-bitbucket-connector-plugin

Hi Everyone,

I would like to update that DVCS Connector version 2.1.4, which includes this fix, has been deployed to all OnDemand instances.

Please let us know if the problem that you face in this issue still exist.

Regards,

Zehua Liu | Atlassian

The internal issue that blocks the deployment of 2.1.4 will be fixed on 28 Apr. We will resume the rest of the DVCS Connector 2.1.4 deployment on 29 Apr.

Hi Guys,

DVCS Connector 2.1.4 has been partially deployed to OnDemand. However, due to some internal issue, we could not finish the deployment, which left about half of the OD instances still having the old version (2.1.2).

We are investigating the issue and will update the status once we have an estimate of when we could complete the deployment.

Regards,
Zehua

I can see the pull requests, but the status is incorrect. They are showing as 'open' even when they have been closed (in some cases for several days). I did a manual resync of the repo in the DVCS admin page, but that didn't help

Still not seeing GitHub pull requests in our OnDemand instance, which I assume has been updated by now (April 15th) with these fixes.

I can not see the pull request, yet.

Pull Requests are still not showing.

We will be starting the deployment soon. Targeting to finish it by the end of the afternoon Sydney EST.

OD Customers do not have to do anything special, as the next hourly synchronization will pick things up. But you could always trigger a Full sync if you want a clean start.

When on 10 Apr (i.e. what time zone)? Do OnDemand customers need to do anything (like resync the repo) to enable this functionality?

Will be deployed to OnDemand on 10 Apr.

Once affected, on the DVCS Accounts page, users will see the following and will not be able to restart the sync unless by deleting and re-adding the organization.