New Feature

Automatically detect if the information contained in attachments is sensitive and encrypt it.

Indicate the number of attachments that are due to be checked by the Encryption Scheduler (Cron), so the admin user has a better understanding of how many files are due to be scanned/checked.

Enable the ability to clone the values of encrypted custom fields between linked issues.

Currently it is not possible to export the encrypted data. Attachments: The workaround is to decrypt all the attachments firstly before exporting them. CustomFields: There is no way to decrypt encrypted custom fields so it is totally impossible to...

Currently, keys are stored in the database in plain text. We need to explore different alternatives for where and how to store these keys securely. Options we are researching: Jira Home: users could load these keys from a separate location, such a...

Ability to encrypt standard and custom Jira native fields.

Provide an audit log or attachment history within the user interface. This feature should include details such as when an attachment or custom field was encrypted. The logs should cover the following information for all attachments whose encryptio...

Have the ability to encrypt certain comments manually Get certain comments automatically encrypted when detecting specific keywords. These keywords could be already set and also the client could have the ability to set them.

This way, admin users can get notifications when a scan is interrupted, for example.