Description:
Currently, when a Jira project key is changed (e.g., from ABC to DEF), all existing references to the old issue key (e.g., ABC-123) in Bitbucket commits, pull requests, and branches lose their automatic linkage to Jira issues. This breaks traceability and the development panel integration for historical work.

Steps to Reproduce:

1. Create a Jira project with issue key prefix ABC.

1. Push commits to Bitbucket referencing that issue key (e.g., commit message: "ABC-123 my test commit").

1. Change the Jira project key from ABC to DEF

1. In Bitbucket, observe that previous commits referencing ABC-123 are no longer linked to Jira.

Feature Request:
Please implement the ability for Bitbucket Cloud to recognize and link to Jira issues using both current and previous project keys, maintaining traceability and integration even after a project key change in Jira.

Business Impact:

• Maintains historical traceability between code and issues.

• Reduces manual effort to maintain links after project key changes.

• Prevents loss of context in development and audit trails.