Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-19809

Data related to repository that is recreated with the same name will not be synced

XMLWordPrintable

      Issue Summary

      Commits, PRs and etc. that is related to a repository that is created with the same name of the deleted repository will not be synced to JIRA.

      Further digging into this matter, it looks like JIRA is able to retrieve the repository name, however, it is not creating the Webhook (for Github/Github Enterprise) and Services (for Bitbucket Cloud) after the repository syncing.

      Steps to Reproduce

      1. Create the JIRA - Github or JIRA - Bitbucket integration.
      2. After the sync is done, delete one of the repositories on Github or Bitbucket.
      3. Refresh the repo list on JIRA.
      4. Create a new repo with the same name on Github or Bitbucket.
      5. Refresh the repo list on JIRA.
      6. Navigate to the repo Webhook (on Github) or repo Services (on Bitbucket) - there will be no Webhook (for Github/Github Enterprise) or Services (for Bitbucket Cloud) created.

      Expected Results

      There will be Webhook (for Github/Github Enterprise) and Services (for Bitbucket Cloud) created for the newly recreated repo with the same name of a deleted repo.

      Actual Results

      Navigate to the repo Webhook (on Github) or repo Services (on Bitbucket) - there will be no Webhook (for Github/Github Enterprise) or Services (for Bitbucket Cloud) created.

      Workaround

      Recreate the JIRA - Github or JIRA - Bitbucket integration.

          Form Name

            [JSWSERVER-19809] Data related to repository that is recreated with the same name will not be synced

            Ankur Jain added a comment -

            I have question on the suggested workaround. Why is it being suggested to recreate GitHub-Jira Integration ? This would mean deleting the existing integration and recreating the integration. This can have broad consequences and potentially impact all existing repositories where webhooks would still be working fine. 

            Instead why not just create the Jira webhook manually on impacted repository ? This way you can be sure that you are not impacting any other repositories.

            Ankur Jain added a comment - I have question on the suggested workaround. Why is it being suggested to recreate GitHub-Jira Integration ? This would mean deleting the existing integration and recreating the integration. This can have broad consequences and potentially impact all existing repositories where webhooks would still be working fine.  Instead why not just create the Jira webhook manually on impacted repository ? This way you can be sure that you are not impacting any other repositories.

              Unassigned Unassigned
              mmuthusamy Moga
              Affected customers:
              4 This affects my team
              Watchers:
              8 Start watching this issue

                Created:
                Updated: