Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-9452

There is no way to update out-of-date info in Jira Server/DC's dev summary panel for old branches

XMLWordPrintable

      Summary

      There is a discrepancy between the data shown in JIRA's dev summary panel and what's really in Bitbucket Server. For old branches/issues, this data will never get refreshed. (This is due to a discrepancy between the AO JIRA_INDEX table and sta_pull_request).

      Note: this only applies to Bitbucket's integration with Jira DC & Server, not Jira Cloud. For sync issues with Jira Cloud see https://jira.atlassian.com/browse/BSERV-14084 

      Environment

      Bitbucket Server 4.6.2 with many 3rd party add-ons

      Steps to Reproduce

      Unknown

      Expected Results

      The data shown in the dev summary panel and the state of PRs in Bitbucket Server should be in-sync.

      Actual Results

      The data shown in the dev summary panel shows the PR as OPEN when it's actually merged

      Workaround

      Bitbucket provides a REST call that reindexes the branches and pull requests in the specified Bitbucket repository, triggering an update in JIRA which in turn updates the JIRA issue's dev summary panel. The REST call must be run as a user with an admin permissions:

      curl -v -u <username> -p -H "Accept: application/json" -H "Content-Type: application/json" -d "{}" <bitbucket URL>/rest/jira-dev/1.0/projects/<project key>/repos/<repository slug>/reindex

      Example for user admin, project TEST and repo TestRepo:

      curl -v -u admin -p -H "Accept: application/json" -H "Content-Type: application/json" -d "{}" <bitbucket URL>/rest/jira-dev/1.0/projects/TEST/repos/TestRepo/reindex

      Notes

      • There was a suggestion that this issue was caused by third-party plugins but we have seen this (rarely) on our internal Atlassian Bitbucket Server instance, so we know it can happen without them, too.
      • Without "steps to reproduce", it's hard to know where to start on this bug. Perhaps we could provide some way to manually refresh the data (with a "reload" button in the dev summary panel?). 

              khughes@atlassian.com Kristy
              abromberg Aaron Bromberg (Inactive)
              Votes:
              37 Vote for this issue
              Watchers:
              64 Start watching this issue

                Created:
                Updated:
                Resolved: