- Fixed bug that affects thumbnails generation
Version history
1.10.5Jira Data Center 8.11.0 - 9.11.32023-11-13Bug fix 1.10.5Jira Server 8.11.0 - 9.11.32023-11-13Bug fix - Fixed bug that affects thumbnails generation
1.10.4Jira Data Center 8.11.0 - 9.10.22023-10-17Bug fixes and analytics - Fixed documentation link
- Fixed JavaScript error in the configuration pages
- Added usage analytics
1.10.4Jira Server 8.11.0 - 9.10.22023-10-17Bug fixes and analytics - Fixed documentation link
- Fixed JavaScript error in the configuration pages
- Added usage analytics
1.10.2Jira Data Center 8.11.0 - 9.10.22023-03-27Configuration redirects improvement Configuration pages redirect to project selection page when keys exist.
1.10.2Jira Server 8.11.0 - 9.10.22023-03-27Configuration redirects improvement Configuration pages redirect to project selection page when keys exist.
1.10.1Jira Data Center 8.11.0 - 9.5.12023-03-07Usability improvements in the attachments encryption process Usability improvements in the attachments encryption process
1.10.1Jira Server 8.11.0 - 9.5.12023-03-07Usability improvements in the attachments encryption process Usability improvements in the attachments encryption process
1.10.0Jira Data Center 8.11.0 - 9.5.12023-02-03New configuration wizard - A new step-by-step configuration wizard, to set up the keys, encrypt attachments, create encrypted custom fields and restrict visibility in a risk-free guided manner.
1.10.0Jira Server 8.11.0 - 9.5.12023-02-03New configuration wizard - A new step-by-step configuration wizard, to set up the keys, encrypt attachments, create encrypted custom fields and restrict visibility in a risk-free guided manner.
1.9.0Jira Data Center 8.11.0 - 9.4.122022-10-27Encrypted fields accessible via API and improved configuration experience - 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.
1.9.0Jira Server 8.11.0 - 9.4.122022-10-27Encrypted fields accessible via API and improved configuration experience - 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.
1.8.0Jira Data Center 8.11.0 - 9.2.12022-09-16Encrypted custom fields and attachments visibility improvements and bug fixes - 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.
1.8.0Jira Server 8.11.0 - 9.2.12022-09-16Encrypted custom fields and attachments visibility improvements and bug fixes - 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
1.7.22Jira Data Center 8.11.0 - 8.22.62022-05-23Bug fixes Bug fixes
1.7.22Jira Server 8.11.0 - 8.22.62022-05-23Bug fixes Bug fixes
1.7.21Jira Data Center 8.11.0 - 8.22.62022-04-08Bug fix Bug fix
1.7.21Jira Server 8.11.0 - 8.22.62022-04-08Bug fix Bug fix
1.7.20Jira Data Center 8.11.0 - 8.20.282022-01-17Bugs fixes - Fixed bug with attachments
1.7.20Jira Server 8.11.0 - 8.20.282022-01-17Bugs fixes - Fixed bug with attachments
1.7.19Jira Data Center 8.11.0 - 8.20.282021-06-23Bugs fixes - Fixed bug with Oracle databases
- Fixed streams that are not properly closed
1.7.19Jira Server 8.11.0 - 8.20.282021-06-23Bugs fixes - Fixed bug with Oracle databases
- Fixed streams that are not properly closed