Request: Please let us know if changing the username will affect your apps - Bitbucket - bit-booster.com

[Oliver Kanschat-Krebs]

Dear Sir or Madam,

I am reaching out to you on behalf of the Atlassian Team at BSH Hausgeräte GmbH. The Atlassian Team is about to perform a large-scale change of usernames in Atlassian Crowd across the entire user base. Naturally, the team would like to understand the impact this has on your app, the data it stores and it uses.

In more detail, we would like to understand how your app references the users in the database. Do you go with the username, which can be updated for a specific user, or do you reference the internal user key/ID. For example, in Jira, this is the app_user.user_key column. Of course, it would be of major interest whether we can expect sound handling of the change of usernames.

For reference's sake, here are two impact examples from Jira and Confluence:

• JRASERVER-70685: Renaming the user should also update filters and mentions

• CONFSERVER-82873: Updating the username breaks user macros

Moreover and to be more specific, the following apps of yours are in use in our systems.

App Name	App-Version
Commit Graph for Bitbucket Data Center	2022.12.05

At the time of writing, the Bitbucket Version in use is v7.21.10. As suggested above, the Bitbucket instance in question is connected to the Atlassian Crowd instance where the change of usernames will be carried out. The latter are planned to be implemented in the 3rd quarter of 2023. Thus, quick feedback would be most highly appreciated.

Finally, we would kindly ask you to include all CC recipients in your reply.

Looking forward to your feedback!

Best regards,
Oliver Kanschat-Krebs
Atlassian Team at BSH

‌

[Julius Davies [bit-booster.com]]

Changing usernames does not affect any of our apps:

• Commit Graph and Git Graph for Jira plugins both do not touch user information in any way.
• PR-Booster also does not touch user information in any way.
• Control Freak can store a "exempt user" list. To implement this it uses the underlying id of the user - it does not use the username or email address.