Issue Summary

Bitbucket Cloud commits does not link to Jira issue after linking a DVCS account.

This is reproducible on Data Center: (yes)

Steps to Reproduce

1. Go to Bitbucket Cloud, create a new repository, and add some commits with Jira issue key in the commit message (e.g SCRUM-8 and SCRUM-9).
   
2. In Jira, there is an existing issue created beforehand such as SCRUM-8 and SCRUM-9.
3. Follow Connect Bitbucket Cloud to Jira Software Server doc to link the DVCS accounts.
4. Wait for all Bitbucket Cloud repositories completed sync to Jira
5. After linking the DVCS accounts, we see no link to Jira issue from commits in Bitbucket Cloud.
6. Until Full Sync is performed on the repository in DVCS repository page, we see the links shown up in the commits:
   

Scenario 2

• Deleting and adding a problematic repository remove the commits link of the existing Jira issue key in Bitbucket cloud.

Scenario 3

1. Add a new repository and add a new commit mentioning SCRUM-1 in the commit message.
2. In DVCS, refresh all the repositories, and the new repo is automatically added there.
3. Go back to the Bitbucket Cloud > new repo and see no commit links to the Jira issue.

Expected Results

• DVCS should have create/update the commit links of the existing Jira issue key in Bitbucket cloud after linking the DVCS accounts.
• Deleting and adding a repository should have create/update the commit links of the existing Jira issue key in Bitbucket cloud

Actual Results

• DVCS did not do create/update the commit link of the existing Jira issue key in Bitbucket cloud after linking the DVCS accounts.
• Deleting and adding a repository did not create/update the commit links of the existing Jira issue key in Bitbucket cloud

Workaround

Performed full sync on the problematic repository to fix the commits link in Bitbucket Cloud for the time being.

Notes

The issue is not reproducible in 8.20.23, 8.22.1, and 9.4.7.