All ideas

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

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

Currently, if a user previously had access to an attachment, specifically an image, and later that access is revoked, they can still view the thumbnail. This is particularly problematic for images, as the content can still be seen in the thumbnail.

When an encryption process, such as the encryption of a new project, is taking too long, it would be beneficial to offer users the ability to stop the process. This would allow users to make configuration changes, for example, and then provide the...

Mask the text of encrypted custom fields while it is being written for an extra layer of security.

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...

Be able to set especific permissions for each of the encrypted custom fields individually or, at least, for each type of encrypted custom field.

Analyze the performance of the app across various Jira instances, considering different sizes, memory capacities, and other variables. Document the results of these performance analyses.

We could add new methods to the current Rest API: Get encrypted projects list Set encrypted projects list (potential security risk) Get storage method (doesn't make sense now because we only allow in database) Set storage method Process status

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...