Data Hosting


Hosting options within the Confidential Fields app

 

Access the hosting menu by selecting Confidential Fields → Hosting in the left Jira navigation.

 

You will see the following hosting options:

Hosting options

Your Jira data residency

This is the default setting. If you use this setting, the Confidential Fields data is encrypted and saved in the currently used Jira data residency database.

On data residency: Atlassian Cloud customers on paid plans can choose their Data residency. European customers can pick Germany/Ireland as data residency. Read the Atlassian documentation for more information.

However, many countries are not listed on the available Atlassian hostings. For example, there is currently no Swiss hosting.

 

Available hostings

Switzerland (Google Cloud)

This option will save the Confidential Field data in the available Swiss hosting (currently Google Cloud). The process is fully automated, and there are no additional costs for you.

Unless otherwise mentioned, all existing and new hosting options will be set up and managed on aiven.io.

On Aiven: Aiven fully manages open source cloud data tools and services (including AWS, Google Cloud, and Microsoft Azure) in a required location. Aiven is compliant with ISO/IEC 27001:2013, SOC 2, GDPR, HIPAA, CCPA, and PCI DSS. This provides an additional layer of security for you as a customer. Read more about Aiven’s Security & Compliance.

More hosting options will appear whenever we have a direct request by customers (see below).

 

Other hosting options

Do you have a different hosting requirement? For example:

  • Do you want to store the Confidential Field data in a self-hosted database?

  • Do you want to use your hosting provider’s database for Confidential Fields?

  • Do you need a database managed by us located in another country?

Please let us know via the feedback form in the app or contact the bitvoodoo Support.

 

Decryption Key

Below the different hosting options, you will find a link “decryption key”. When clicked, an overlay will appear:

The values of the Confidential Fields are encrypted with AES 256 and saved in the selected hosting database. 
bitvoodoo ag does not store your decryption key and cannot read the values. Only your Jira users can read the values. Read more about this on the page Data Encryption.

Please save the string “Your decryption key” in a secure location. This will allow you to decrypt custom field data outside of Jira.

You can also access this overlay from the "Confidential Fields" menu at any time.

The values of the Confidential Fields are encrypted and can only be read within Jira. Therefore, they cannot be read via the Jira API. Would you like to read the Confidential Fields values outside of Jira using an API? Please let us know in the feedback form or contact the bitvoodoo Support. We will create a custom API for future app versions if there is sufficient interest.

 

How to change the data hosting in the app

  1. To change the hosting, tap the “Change hosting” button.

  2. In the drop-down menu, choose a different hosting option.

  3. Save your selection by tapping the “Save” button.

  4. A confirmation message will appear. Tap “Access Confidential Fields” to get an overview of Confidential Fields.

Data import when changing the hosting

If you have created Confidential Fields in the past and decide to change the hosting at a later stage, a popup will appear:

 

 

You can now decide to export the Confidential Fields' data (recommended). Tap the Export button and save the file to a secure location.


If you don’t export and tap “Continue”, the data in the existing Confidential Fields is lost (the Confidential Fields themselves will remain). So you should only do this if you want to reset the data.

In the next step, the app asks you to import the exported file. Note that a later import is not possible. Choose the exported file and tap “Import”.

 

If the import was successful, you will see “The selected new hosting is now active, and the Confidential Fields are restored.”


 

Back to the main documentation