@Brent if this works as designed then maybe you should rethink yours design approach..from my end-user experience I can say that development panel and integration for git func. in combination with App Link and QAuth is just a disaster and cause issues for many of us.

Bitbucket over App Link does not support automation tasks ..so we need QAuth..however having this both enabled in any combination  does not lead to desired solution:

Having commits/created branches/PR in real-time (as soon they are created)
Having historical commits,branches
Having NO duplicate development info's
Having automation task working

Having no delays on events (commit,create branch, PR etc)
Having NO need to close, refresh ticket to get development Info updated (never heard about frames ??? which can be independent and self refreshing???)

On some point you guys need to decide to rewrite development panel, either fix QAuth part or move all functionality to App Link and make things working..at current state I see this as very poor quality tbh

This is also a problem if you neglected to turn off the Commit details for the AppLink connection while on cloud, and didn't have the Oauth integration running for a time. When you then later set them up properly, and turn off commit details to avoid duplication, the older (but created while on cloud) commit details generated while just AppLinks was running will disappear. It would be good to be able to provide those on the cloud integration side.

This is working as designed because backfilling old commit data will be incredibly expensive for the server.

We've put this issue in "Gathering impact" status in order to hear from affected customers and understand the impact. We'll consider improving this based the feedback we receive.