- Improved (encryption and decryption) process performance
- Improved progress bar in order to show the currently in progress attachment id
Version history
1.7.15Jira Data Center 7.3.0 - 8.8.12020-06-01Process improvements 1.7.15Jira Server 7.3.0 - 8.8.12020-06-01Process improvements - Improved (encryption and decryption) process performance
- Improved progress bar in order to show the currently in progress attachment id
1.7.14Jira Data Center 7.3.0 - 8.8.12019-12-04Cloning the issue bug has now been fixed No release notes.1.7.14Jira Server 7.3.0 - 8.8.12019-12-04Cloning the issue bug has now been fixed No release notes.1.7.13Jira Data Center 7.12.3 - 8.5.42019-10-01Bug fixes - Fixed bug managing permissions
- Fixed bug displaying text area encrypted fields in customer portals
1.7.13Jira Server 7.3.0 - 8.5.42019-10-01Bug fixes - Fixed bug managing permissions
- Fixed bug displaying text area encrypted fields in customer portals
1.7.12Jira Data Center 7.12.3 - 8.2.62019-06-11New features, data center compatibility and 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
1.7.12Jira Server 7.3.0 - 8.2.62019-06-12New features, data center compatibility and 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
1.7.7.1Jira Server 7.3.0 - 8.0.32019-04-16Visibility restrictions for attachments 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.
1.7.6Jira Server 7.3.0 - 8.0.32019-02-25Project Level Encryption for attachments and JIRA 8 compatibility 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
1.7.4Jira Server 7.3.0 - 7.13.132019-01-08New custom field type and new health check process 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.
1.7.3Jira Server 7.3.0 - 7.13.132018-11-09Thumbnails improvement and bug fix 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
1.7.2Jira Server 7.3.0 - 7.12.32018-10-30Bug fixes for Windows servers Bug fixed:
* Error when decrypting all attachments on Windows Servers
1.7.1Jira Server 7.3.0 - 7.12.32018-10-08Improvement for the customer portal of JSD and bug fix 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
1.7.0Jira Server 7.3.0 - 7.12.02018-09-17Restore Keys, Key Rotation and your keys are stored in memory. 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)
1.6.4.2Jira Server 7.3.0 - 7.11.22018-08-29Bug fixed Fixed bugs:
- CSV and XML export encrypted values
- Bug sharing issues from the customer portal
1.6.4.1Jira Server 7.3.0 - 7.11.22018-08-20Bug fixed 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