Environment

• Jira Software 8.2
• Fisheye / Crucible 4.7.0
• Bitbucket 6.3.2

Steps to reproduce

1. Install and connect Jira, Bibtucket and Fisheye
2. Connect Bitbucket's repository to Fecru according to Setting up a Git repository in Crucible
3. In your checked-out code, create a branch and push it to Bitbucket
   • At this point, Jira should show only one Branch (from Bibtucket)
4. Add a file to the repository, commit it and push it to the branch
   • Jira should then display 2 branches (one from "Fisheye / Crucible" and one from "Bitbucket Server")
5. Then, checkout a different branch locally, and delete the branch used previously from local and remote
   • In Jira, the Development panel will show 1 branch, but clicking it will show You don't have access to view all related branches. Please contact your administrator.

Expected Behavior

Jira should not display any branches on the related issues

Actual Behavior

Jira still shows 1 branch, but clicking on it shows:

You don't have access to view all related branches. Please contact your administrator.

Notes

• The repository in Fecru correctly doesn't display the branch information immediately after it's removed
• Reindexing the repository in Fecru will remove the references to the commited file, but will not impact Jira
• In Jira's database we can see:

  WITH applinks AS (SELECT SUBSTR(a.property_key,16,36) as "appkey", b.propertyvalue as "appname" FROM propertyentry a join propertystring b on a.id=b.id where a.property_key like 'applinks.admin%name')
  
  SELECT a.appname, s."UPDATED", s."JSON" FROM "AO_575BF5_DEV_SUMMARY" s 
  JOIN applinks a ON a.appkey = s."PROVIDER_SOURCE_ID"
  WHERE "JSON" like '%SCRUM-28%';
  

    appname  |         UPDATED         |                                                                                                                                            JSON
  -----------+-------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
   FeCru     | 2019-06-26 10:32:08.512 | {"value":{"targets":{"SCRUM-28":[{"type":{"id":"repository"},"objects":[]},{"type":{"id":"review"},"objects":[]},{"type":{"id":"branch"},"objects":[{"lastUpdated":"2019-06-26T10:30:54.000+0200","count":1,"branches":["feature/SCRUM-28-create-song"]}]}]}},"expiry":9223371721494775807}
   Bitbucket | 2019-06-26 10:35:02.405 | {"value":{"targets":{"SCRUM-28":[{"type":{"id":"repository"},"objects":[]},{"type":{"id":"branch"},"objects":[]},{"type":{"id":"pullrequest"},"objects":[]}]}},"expiry":9223371721494775807}
  (2 rows)
  

Workaround

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