Summary
Customers want to use Atlassian Intelligence / Rovo Dev on most repositories in a Bitbucket Cloud workspace, but exclude specific sensitive repos from any AI processing. Today, controls exist only at org/product, workspace, and some per‑feature levels; there is no general per‑repository "AI opt‑out". As a result, customers must split repos across multiple workspaces (AI vs non‑AI), which adds admin overhead and blocks/limits AI adoption for compliance‑sensitive teams.

Requested capability

• A repository‑level setting to:
  • Fully disable all AI features for that repo, or
  • have Atlassian Intelligence enabled only for specific repos in a workspace.

• When a repo is marked AI‑restricted:
  • Its data must not be used by any AI feature or AI training/eval pipelines.

• Workspace‑level visibility:
  • Overview of which repos are AI‑enabled vs AI‑restricted.
  • Ability to define defaults for new repos.

• Auditability:
  • Log who changed AI settings on which repos and when.