Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

This page describes what private and secret data is accessed or stored by the app and for what purposes. 

Bitbucket Access Token

BDD for Jira with Git app makes use of a Bitbucket access token for authorizing of upload and download API requests with Bitbucket. This token is added to the app’s configuration via Jira project settings page, see related information on page - Enable Git Integration

The access token is entered in plain text via the configuration screen however it is saved in an encrypted form using Atlassian Forge platform’s secret store utility, see more information here.

Once saved it is not shown again on successive access to the App’s settings page, but message is shown confirming that access token is present in configuration, like shown below.

image-20250206-164929.png

Access to user’s email address

The app accesses user’s email address that is configured in Jira. This is used to populate commit’s author email field whenever a change is uploaded to Bitbucket from Jira. Each Git commit must have a username and an email address. The email address is only accessed at the time when a user actually makes a change to the Feature field in Jira and the project is configured with a linked Bitbucket repository in app’s settings.

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.