Configure Encryption for Jira
Encryption for Jira can be easily configured. Follow these steps to get started:
AWS S3 storage
We currently support storing attachments only in the local file system and not in Amazon S3. Keep an eye out for further development. đź‘€
Key Configuration
Encrypt Attachments
Select Encrypt Attachments from the homepage or the left navigation options to begin this task.
On this screen, you can encrypt all attachments in your Jira instance or only those in selected projects.
To encrypt all attachments:
To encrypt specific attachments:
Encrypt Custom Fields
Encrypted fields must be added to projects; you cannot encrypt existing fields.
Visibility Permissions
Visibility permissions let you decide who can see attachments and encrypted custom fields. Until you change these settings, Jira will continue to work as it did before you installed Encryption for Jira.
Users can see the attachments or encrypted custom fields when the toggles are activated. Only users with access permissions can see when the toggles are off.
Issue Cloning
Since version 2.0.0 of Encryption for Jira, when Issues with Attachments are cloned, Encryption for Jira will ensure the attachment author is preserved on the cloned Issue. By default, Jira assigns the cloning user as the author of the attachments, bypassing Attachment Visibility Permissions.
Encryption Scheduler
The Encryption Scheduler automates the process of encrypting applicable attachments.
Set up the Encryption Scheduler to run at your convenience. Note that changes cannot be made in Encryption for Jira while the process is taking place.