Feature Improvement

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.

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

Offer more types of encrypted custom fields, such as: Selected lists fields Checkbox fields Cascade select fields Single/multi select fields JWT calculated number/date fields Insight fields Encrypted number fields (confidential budget, salaries, e...