Duplicate branches commits, and pull requests when synching Jira with GitHub

Issue Summary

After upgrading Jira to 8.14.x, there are duplicated repositories, commits, pull requests showing in the Development panel from the issues.

When checking the database, we confirm data is duplicated as well:

SELECT 
    om.name AS "Org Name"
    , rm.name AS "Repo Name"
    , rm.slug
    , rm.organization_id
    , rm.fork
    , rm.deleted
    , rm.last_commit_date
FROM AO_E8B6CC_REPOSITORY_MAPPING rm, AO_E8B6CC_ORGANIZATION_MAPPING om
WHERE om.id = rm.organization_id AND rm.NAME = '<repo-name>';

Affects GitHub accounts only.

Steps to Reproduce

Steps to Reproduce

• Upgrade to Jira 8.14
• Set up a DVCS integration with Github
• Commit to repository
• Github Webhook automatically pings DVCS and syncs
• Click on Issues > Development panel, the commits will show twice:
  

Expected Results

Repositories commits pull requests to appear once

Actual Results

GitHub does not fetch the correct organization as it was based on the host URL - which for multiple orgs is the same. Thus some organizations end up with duplicated repositories.

Repositories are duplicated in the database as well.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available