You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: add Bitbucket to the Pro Integrations pages (#15207)
Adds Bitbucket to the supported integrations lists and documents the
setup: instance credentials (Atlassian account email plus a scoped API
token, since app passwords are deprecated), the workspace and repository
slug mapping fields, the requirement to enable the repository issue
tracker, and the default severity to priority and status to state
mappings.
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/content/issue_tracking/pro_integration/integrations_toolreference.md
+46Lines changed: 46 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -48,6 +48,52 @@ The attributes in the form are supplied as defaults and are as follows:
48
48
-**False Positive Mapping**: `Done`
49
49
-**Risk Accepted Mapping**: `Done`
50
50
51
+
## Bitbucket
52
+
53
+
The Bitbucket integration allows you to push issues to the [issue tracker](https://support.atlassian.com/bitbucket-cloud/docs/enable-an-issue-tracker/) of a Bitbucket Cloud repository.
54
+
55
+
The issue tracker is optional in Bitbucket and must be enabled on the repository before DefectDojo can create Issues in it. To enable it, open the repository in Bitbucket and select **Repository settings**, then enable the issue tracker under **Features**.
56
+
57
+
### Instance Setup
58
+
59
+
-**Label** should be the label that you want to use to identify this integration.
60
+
-**Location** should be set to `https://bitbucket.org`.
61
+
-**Email** should be the email address of the Atlassian account that the API token belongs to.
62
+
-**API Token** should be set to a scoped Atlassian API token.
63
+
64
+
Bitbucket app passwords are deprecated by Atlassian and will not work with this integration. To create an API token:
65
+
66
+
1. Open [Atlassian account settings](https://id.atlassian.com/manage-profile/security/api-tokens) and choose **Security**, then **Create and manage API tokens**.
67
+
2. Choose **Create API token with scopes**, name the token, and set an expiry date.
68
+
3. Select **Bitbucket** as the app.
69
+
4. Grant the token permission to read repositories and to read and write issues.
70
+
71
+
### Issue Tracker Mapping
72
+
73
+
-**Workspace** should be the slug of the workspace that contains the repository, as it appears in bitbucket.org URLs.
74
+
-**Repository Slug** should be the slug of the repository that you want to create Issues in.
75
+
76
+
### Severity Mapping Details
77
+
78
+
This maps to the Bitbucket issue Priority field. The attributes in the form are supplied as defaults, and each value must be one of Bitbucket's priorities: `trivial`, `minor`, `major`, `critical`, or `blocker`.
79
+
80
+
-**Severity Field Name**: `priority`
81
+
-**Info Mapping**: `trivial`
82
+
-**Low Mapping**: `minor`
83
+
-**Medium Mapping**: `major`
84
+
-**High Mapping**: `critical`
85
+
-**Critical Mapping**: `blocker`
86
+
87
+
### Status Mapping Details
88
+
89
+
This maps to the Bitbucket issue State field. Each value must be one of Bitbucket's issue states: `new`, `open`, `resolved`, `on hold`, `invalid`, `duplicate`, `wontfix`, or `closed`.
90
+
91
+
-**Status Field Name**: `state`
92
+
-**Active Mapping**: `new`
93
+
-**Closed Mapping**: `resolved`
94
+
-**False Positive Mapping**: `invalid`
95
+
-**Risk Accepted Mapping**: `wontfix`
96
+
51
97
## GitHub
52
98
53
99
The GitHub integration allows you to add issues to a [GitHub Project](https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects), which also open Issues in an associated Repo. These Repos/Projects can be associated with either a GitHub Organization or a personal GitHub account.
0 commit comments