問題

When looking at the Development Panel in a Jira issue, information such as commits (from either Fisheye or Bitbucket), branches (from either Fisheye or Bitbucket), Crucible reviews and Bitbucket pull requests may appear outdated, for example:

• The number of commits (from either Fisheye or Bitbucket), branches (from either Fisheye or Bitbucket), Crucible reviews and Bitbucket pull requests reported is incorrect
• When viewing extended information about commits (from either Fisheye or Bitbucket), branches (from either Fisheye or Bitbucket), Crucible reviews and Bitbucket pull requests, the information in the extended panel is different to what is shown in the panel summary.
• Jira shows incorrect states for Bitbucket Pull Requests or Crucible reviews. 
• There are existing commits (from either Fisheye or Bitbucket), branches (from either Fisheye or Bitbucket), Crucible reviews and Bitbucket pull requests for the issue, but Jira does not show any.

原因

Jira relies on two mechanisms to stay in sync with Bitbucket and with Fisheye/Crucible:

1. Real-time updates submitted by Bitbucket (or Fisheye/Crucible) to Jira via the application link.
2. Scheduled background job that sweeps all changes that were not processed by real-time updates since the last run.

Sometimes, real-time updates may fail for whatever reason, and the background sync may also not be working. The combination of internal and external factors may result in the development information cached in Jira to not be accurate anymore.

回避策

If the problem of development information being outdated only reported for few incidents, the quickest way to solve it is to drop the cached information in Jira via direct database modification by an issue key (PROJECT-435123 in this case):

DELETE FROM AO_575BF5_DEV_SUMMARY WHERE JSON LIKE '%PROJECT-435123%';

It is safe to run DELETE operations on AO_575BF5_DEV_SUMMARY table as it only stores cached information from Bitbucket and from Fisheye/Crucible, that can be re-synced again. Make sure you only drop 1 record per issue key affected.

Once the cache is dropped, next time the issue view page is accessed, the development information will be refreshed from Bitbucket (or Fisheye/Crucible).

ソリューション

If the issue appears for many random issues, or there are issue with the background job operation, please contact Atlassian Support to run a comprehensive analysis of the system.