Documentation Index

Fetch the complete documentation index at: https://help.nucleussec.com/llms.txt

Use this file to discover all available pages before exploring further.

BitBucket Issues

  • 1 minute(s) read
Prev Next

  1. Open a browser and login to BitBucket.

  2. Browse to your avatar, then click on BitBucket Settings.

bitbucket-personal-settings.png

  1. Click on the menu item under "Access Management" labelled App Passwords

bitbucket-app-password-option.png

  1. On the resulting page, click on Create App Password

bitbucket-app-password2.png

  1. Enter a name in the label for you to remember what this connection is.

  2. Check the following boxes

Team Membership > Read
Repositories > Read
Issues > Write & Read

  1. The result should look something like this:

bitbucket-app-password.png

  1. Click Create

  2. Copy the resulting App Password to your clipboard.

  3. In a 2nd browser window, open Nucleus and browse to Project Administration > Connectors.

  4. Under the Issue Trackers section, click the BitBucket icon.

  5. In the Setup BitBucket Connector popup, complete the following fields:

Attention

If you are using the Nucleus Agent, please refer to the document here

Field Description
BitBucket URL Enter the URL to the api of your BitBucket server or cloud instance.
Project Enter in the project name for which this connector is set up. For example, rampant/demo.
Application Password Enter the password which was generated in the BitBucket console (the one copied to your clipboard).

  1. Click the "Save Connection" button and wait for the Success message.

  2. Click the "Verify Connection" button. You will be a message to notify you that the connection test was successful. Your connector is now setup properly.

  3. Optional: Select a user from the Default Assignee dropdown menu in order to have that user be the default user when manually assigning issues so you don't have to select from the dropdown every time.

  4. Close the popup window.

Attention

Only users which are on the repo's team will be able to have tickets assigned to them. BitBucket does not allow for users which are not on the team but assigned to the repo to be accessed through the API.