Migrating BitBucket issues to JIRA broke issue/commit links

[Jacob]

I was quite saddened to discover that after migrating BitBucket issues to JIRA issues none of the "smart links" like issue #123 or commit SHA `deadbeefcafe...` seem to be there any more. I don't want to waste time re-associating everything issue we've ever created in the past 5 years, ug... any way to retroactively fix or do we just have to move on and let the old eventually fall off?

The commit history is full of messages like, `fix: don't use deprecated APIs (fixes #1234)` where 1234 was the BitBucket issue tracker issue ID. I expected the JIRA issue migration process to track the old BitBucket ID so that it could preserve this very useful feature (which, TBH, is table stakes because we're all so used to it from GitHub).

Similar to https://community.atlassian.com/t5/Jira-questions/What-links-a-JIRA-issue-to-Bitbucket-commits-PRs/qaq-p/629638