Issue Summary

There is currently no backfill of data with OAuth.
Data starts getting sent from the moment the OAuth connection is established.
Applinks can show old data because the data is queried directly from Bitbucket when users view the issue.
OAuth doesn't do this.

This is reproducible on Data Center: yes

Steps to Reproduce

1. Applink Bitbucket DC to Jira DC
2. Populate Data
3. Migrate Jiras On-Prem to Jira Cloud
4. Check Dev Panel for data

Expected Results

There is no stale data or missing data

Actual Results

There is stale data eg. issues unresolved and merged PRs show as open OR
There is missing data eg. data prior to migration from Jira On-Prem to Cloud

Workarounds

Application Tunnels should allow the development information functionality that Application Links allow.
As such there are workarounds that might help given either is enabled:

First Workaround
https://confluence.atlassian.com/bitbucketserverkb/reindex-jira-issue-keys-in-bitbucket-server-datacenter-779171709.html <- here you will remove the snapshot file which will trigger Bitbucket to rebuild and send the datasource that is needed for Jira to update the dev panel

The caveat here is that though it is useful for 1 or 2 repos, it can incur significant overhead for many repos.

Second Workaround
The first workaround will only target commit data. To target pr data the instructions here must be followed:
https://confluence.atlassian.com/bitbucketserverkb/the-number-of-pull-requests-or-branches-differ-between-jira-development-panel-overview-and-details-1041078861.html

Caveats

• If development information is enabled in both OAuth and Applinks/Application Tunnel then duplicate data will be seen in the Jira UI dev panel (see troubleshooting section of this resource):
  https://confluence.atlassian.com/bitbucketserver/link-bitbucket-with-jira-776640408.html

• If the OAuth dev panel information is disabled, the duplicate data should be removed but relying on just Applink/Application Tunnel integration for this data entails a latency between when the commit is pushed to Bitbucket and when it is displayed in Jira UI.