Bitbucket export

Before choosing Bitbucket

Use Bitbucket export only for Bitbucket Cloud repositories that have issue tracking enabled. Targets named `bitbucket_data_center_issues` or `bitbucket_server_issues` should not use this native issue export path; send those teams to Jira export or portable fallback unless a customer-owned Cloud issue tracker is available. Start from `/reports/{report}/ticket-exports` after the report finding or generated fix task is ready for external remediation. Do not approve Bitbucket export until the workspace, repository and issue tracker state are clear.

Export a Bitbucket Cloud issue

Follow the path `Ticket export source → Bitbucket Cloud target → Repository mapping → Duplicate check → Bitbucket issue or fallback`.

1. Open /reports/{report}/ticket-exports and select the report issue or generated fix task that belongs in Bitbucket Cloud issues. Result: source_type, source_id, severity, affected URL and evidence-safe links are visible before Bitbucket receives work.
2. Choose an active bitbucket_cloud_issues or bitbucket_issues target for the same account and project. Result: provider_key confirms the target is Bitbucket Cloud issue tracking.
3. Confirm the repository has Bitbucket Cloud issue tracking enabled. Result: unsupported Bitbucket Data Center or Server targets are routed to Jira export or portable fallback instead.
4. Set workspace and repository_slug before export. Result: Bitbucket knows which repository owns the issue.
5. Map component, priority, milestone and assignee when the repository exposes those fields. Result: the Bitbucket issue lands in the right queue with useful routing context.
6. Review title, affected URL, evidence-safe links and acceptance criteria. Result: the issue body is useful without exposing raw private artifacts or secrets.
7. Check external_issue_id and TICKET_EXPORT_DUPLICATE before approval. Result: repeat exports update or link the existing Bitbucket issue instead of creating duplicate repository work.

Map Bitbucket Cloud issue fields

Bitbucket Cloud export needs a repository and issue fields that match the repository's issue tracker.

• workspace identifies the Bitbucket Cloud workspace that owns the repository.
• repository_slug identifies the repository with issue tracking enabled.
• component should map the affected product area when the repository exposes components; review component, milestone, priority and assignee together when those fields are available.
• priority should reflect WebRiskOps severity so high-risk findings do not arrive as unprioritized work.
• external_issue_id links repeat exports back to the existing Bitbucket issue instead of creating duplicate work.
• Issue body should include title, affected URL, evidence-safe links, source identifiers and acceptance criteria.

Ready Bitbucket export states

Continue only when Bitbucket Cloud issue tracking is available.

• Bitbucket Cloud target ready means bitbucket_cloud_issues or bitbucket_issues is active for the same account and project as the report.
• Repository mapping ready means workspace and repository_slug point to a repository with issue tracking enabled.
• Field mapping ready means component, priority, milestone and assignee are valid for the selected repository when configured.
• Preview ready means the issue body is evidence-safe and includes acceptance criteria.
• Duplicate reference ready means an existing external_issue_id can be opened or updated through Status sync and duplicate handling.

Blocked Bitbucket states

Bitbucket must stop when the selected deployment cannot support native issue export.

• `bitbucket_repository_mapping_missing` means choose a workspace and repository before export.
• `bitbucket_target_inactive` or `bitbucket_credential_missing` means reconnect Bitbucket before retrying.
• Bitbucket Data Center and Server do not provide a native issue tracker API for ticket export; connect Jira or choose Bitbucket Cloud issues for repositories with the issue tracker enabled.
• If Bitbucket cannot find the selected repository, issue tracker, milestone or component, refresh mapping and retry.
• Use `portable_export` when the repository does not support Bitbucket Cloud issues.
• Secret or private artifact in preview means redact evidence before creating or updating the Bitbucket issue.

Continue after Bitbucket export

Continue to Work management export when the customer tracks remediation outside developer issue trackers. Use Portable export fallbacks when Bitbucket Cloud issues are unavailable, Status sync and duplicate handling when a Bitbucket issue already exists, and Jira export when the customer uses Bitbucket Data Center or Server with Jira for issues.