Issue Summary

In specific scenarios, during a DVCS sync between Jira and Bitbucket Cloud, the DVCS Connector Plugin can automatically update the DVCS Account Name from a Human-Readable value to a UUID.

When this happens, future syncs will fail until the account is deleted and re-added manually.

Steps to Reproduce

Pre-req: Bitbucket Cloud OAuth Consumer created with Repositories (Read), Pull requests (Read), Account (Read) permissions.

 1.  Link the DVCS Account in Jira: Admin → Applications → DVCS Accounts
 2.  Click "Link Bitbucket Cloud account"
 3.  Enter Client ID and Client Secret from your Bitbucket OAuth Consumer → click Add
 4.  Complete the Bitbucket OAuth authorisation in the popup
 5.  Account appears in the DVCS list
 6.  Click Sync on the new account (or wait for the scheduler)
 7.  ✅ Account name changes to UUID e.g. {3228b2f5-a32c-4261-891c-74077b540486} 

Expected Results

The Account Name is always the human-readable version of the Account Linked

Actual Results

The Account Name change happens silently as if it was a successful write operation.  The only evidence in the log is the JIRA-STATS entry which shows the UUID already baked into the repo display name in the performance metrics:

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available