Upcoming Change: Bitbucket Repository Attributes Now Use Workspace-Scoped Search in Assets

[#1]

Beginning August 24, 2026, we’re starting a rollout that updates Bitbucket Repository attributes in Jira Service Management Assets to use Bitbucket workspace-scoped search.

What’s changing

Bitbucket Repository attributes will search only the Bitbucket workspaces configured for that attribute. This update helps Assets continue to work with Bitbucket Cloud’s current API model and gives admins more control over which workspaces are available for each attribute.

Existing repository values on Assets objects will remain unchanged. Where possible, we’ll automatically populate workspace configuration from the repositories already in use.

Who is affected

This change affects commercial Jira Service Management Assets Cloud customers who use Bitbucket Repository attributes in their Assets schemas. Bitbucket is not available in FedRAMP, so FedRAMP customers are not affected.

What you need to do

Most customers should not need to take action. If an expected repository does not appear after the update, an Assets administrator can review the Bitbucket workspace configuration for that Bitbucket Repository attribute and add the required workspace. Users must also have access to a configured Bitbucket workspace to see its repositories.

What is not changing

• Existing repository values stored in Assets will remain unchanged.
• You can continue to use Bitbucket Repository attributes in Assets.

Learn more

• Read Bitbucket Cloud’s announcement about the end of life for cross-workspace APIs.
• Read Assets support documentation about this change. 

Need help?

If you need help configuring Bitbucket workspaces or troubleshooting repository visibility, contact Atlassian Support with your Assets object schema, object type attribute, Bitbucket workspace, and an example repository that is missing.