• Encrypted fields accessible via Jira API: Until now, the only way to get your unencrypted values was through the Jira user interface. But not anymore! Now you can retrieve your data using Jira REST and Java APIs. It’s the same as retrieving encrypted attachments. So, now you can copy your unencrypted data over to other fields and use it with third-party integrations, automations, or scripts.
• Improved configuration experience: When encryption for Jira is first installed it will no longer encrypt anything until you have completed the configuration. This means your Jira instance will continue to work as before until you are ready to start encrypting your data.

• Encrypted fields accessible via Jira API: Until now, the only way to get your unencrypted values was through the Jira user interface. But not anymore! Now you can retrieve your data using Jira REST and Java APIs. It’s the same as retrieving encrypted attachments. So, now you can copy your unencrypted data over to other fields and use it with third-party integrations, automations, or scripts.

• Improved configuration experience: When encryption for Jira is first installed it will no longer encrypt anything until you have completed the configuration. This means your Jira instance will continue to work as before until you are ready to start encrypting your data.

• Compatibility with Jira 9
• New checkbox to control the visibility of attachments from the Jira Service Management's customer portal: if checked, attachments will be visible from the customer portal (as Jira's normal behavior). If not checked, only those customers granted with the 'Access attachments' permission will be able to see attachments from the customer portal. IMPORTANT: by default this checkbox will be set to 'No'
• Updated the behavior of the checkbox that controls the visibility of encrypted custom fields from the Jira Service Management's customer portal: if checked, encrypted custom fields will be visible from the customer portal (as Jira's normal behavior). If not checked, only those customers granted with the 'Access encrypted custom fields' permission will be able to see encrypted custom fields from the customer portal. IMPORTANT: by default this checkbox will be set to 'No'
• Fixed bug when making the value of encrypted-password custom fields visible during issue creations.

• Compatibility with Jira 9
• New checkbox to control the visibility of attachments from the Jira Service Management's customer portal: if checked, attachments will be visible from the customer portal (as Jira's normal behavior). If not checked, only those customers granted with the 'Access attachments' permission will be able to see attachments from the customer portal. IMPORTANT: by default this checkbox will be set to 'No'
• Updated the behavior of the checkbox that controls the visibility of encrypted custom fields from the Jira Service Management's customer portal: if checked, encrypted custom fields will be visible from the customer portal (as Jira's normal behavior). If not checked, only those customers granted with the 'Access encrypted custom fields' permission will be able to see encrypted custom fields from the customer portal. IMPORTANT: by default this checkbox will be set to 'No'
• Fixed bug when making the value of encrypted-password custom fields visible during issue creations

Bug fixes

Bug fixes

Bug fix

Bug fix

• Fixed bug with attachments

• Fixed bug with attachments

• Fixed bug with Oracle databases
• Fixed streams that are not properly closed

• Fixed bug with Oracle databases
• Fixed streams that are not properly closed

• Latest Jira versions compatibility
• Error displaying progress info
• Error after enabling the project selector checkbox

• Latest Jira versions compatibility
• Error displaying progress info
• Error after enabling the project selector checkbox

New app documentation link

New app documentation link

• Fixed an error when choosing "Encrypt later" after the keys are generated
• Some labels improvements in the configuration page

• Fixed an error when choosing "Encrypt later" after the keys are generated
• Some labels improvements in the configuration page

• Improved (encryption and decryption) process performance
• Improved progress bar in order to show the currently in progress attachment id

• Improved (encryption and decryption) process performance
• Improved progress bar in order to show the currently in progress attachment id

• Fixed bug managing permissions
• Fixed bug displaying text area encrypted fields in customer portals

• Fixed bug managing permissions
• Fixed bug displaying text area encrypted fields in customer portals

• Thumbnails improvement: attachment thumbnails will be shown as they are by default Jira. The lock icon won’t be shown unless a user doesn’t have the “Access attachments” permission.
• Visibility restrictions for custom fields: New permission type 'Access encrypted custom fields', by which administrators will be able to decide who can see and edit the values of the encrypted custom fields. See the documentation for more details.
• New custom field type 'Encrypt Password Field'
• Importing issues from external systems: attachments of issues imported from external systems (CSV, JSON, Bugzilla, MantisBT, Trac, Pivotal Tracker, FogBugz and FogBugz On Demand) will be encrypted on the fly. For the import methods not listed above, the imported attachments will continue being encrypted by the scheduled background process.
• Cloned issues: thumbnails of cloned issues are now displayed
• Encryption keys: improved the encryption keys generation process
• Data center compatibility
• Bug fixes

• Thumbnails improvement: attachment thumbnails will be shown as they are by default Jira. The lock icon won’t be shown unless a user doesn’t have the “Access attachments” permission.
• Visibility restrictions for custom fields: New permission type 'Access encrypted custom fields', by which administrators will be able to decide who can see and edit the values of the encrypted custom fields. See the documentation for more details.
• New custom field type 'Encrypt Password Field'
• Importing issues from external systems: attachments of issues imported from external systems (CSV, JSON, Bugzilla, MantisBT, Trac, Pivotal Tracker, FogBugz and FogBugz On Demand) will be encrypted on the fly. For the import methods not listed above, the imported attachments will continue being encrypted by the scheduled background process.
• Cloned issues: thumbnails of cloned issues are now displayed
• Encryption keys: improved the encryption keys generation process
• Data center compatibility
• Bug fixes

New feature:

• Visibility restrictions for attachments: Added a new permission type, 'Access attachments', by which administrators will be able to decide who can open the attachments. See the documentation for more details.

Bug fixes:

• Problem with SQLServer.

Improvements:

• New project level encryption configuration: admins are able to choose which projects will be encrypted and which ones will not.
• Decrypt/Encrypt all process improvement: Decrypt all and Encrypt all buttons are replaced with the new project level encryption functionality.

Compatibility:

• Encryption for Jira is now JIRA 8 compatible

Bug fix:

• Fixed bug in the configuration screen

Improvements:

• New custom field type: Encrypted Text Field (multi-line)
• New background process that checks the health of the encrypted files.
• New menu option, 'Cron Configuration', where the above process can be configured.
• Database tables optimization.

Improvement:

* Thumbnails for pictures are replaced with the default thumbnail (lock) when running the 'encrypt all' process

Bug fixed:

* Fixed error accessing the configuration page

Bug fixed:

* Error when decrypting all attachments on Windows Servers

New functionality:

• New checkbox in the configuration screen where the administrators can decide if the customers can see the decrypted values in the customer portal

Bug fixed:

• Bug related to the download of attachments that are not pictures

New Functionalities

• Separate attachment and custom field keys.
• Store keys in memory.
• Key rotation. Now you can change the keys.
• Restore Key. If you don't remember the keys, please, contact with us.

Bug Fixes

• SQL Error "Encrypted" Field missing in AO after FS Error
• JIRA Service Desk client cannot see attachments.
• Duplicated names error on download all (zip file)

Fixed bugs:

• CSV and XML export encrypted values
• Bug sharing issues from the customer portal

Enhancements

• Change encryption method for files, from DES to AES. In order to make a stronger security, we have change the encryption method. [more info]

New Functionalities

• New searcher for custom fields.
• Rotate IV. This functionality adds more security in our system. Right now, we have one IV for each encrypted object (file, custom field).
• New encrypted fields history tab.

Bug Fixes

• Validation in administration screen, Key must be 32 characters.
• Problem when plugin is disable/uninstalled (previously all files are decrypted)

Note (if you have 1.6.2 version) :

Please, visit:

https://devoog.com/wp-content/uploads/2018/07/ENC-Upgradefrom1.6.2to1.6.3-090718-1348-6026.pdf