In this release,
Integrated Jira Service Management (JSM) approval history into External Share by utilizing the REST API endpoint:
GET /rest/servicedeskapi/request/{issueIdOrKey}/approval. |
Approval history is now displayed under the Activity tab alongside comments, work logs, and changelog.
Ensured the approval history is effectively positioned for seamless visibility and access within the shared page.
We have improved the zooming and scrolling functionality on the mobile version, making it easier to upload attachments and add comments. Additionally, scaling and the visibility of the ‘Upload a file’ button have been enhanced for better usability.
Updated the preview functionality to display content from secured shares, ensuring the preview accurately reflects shared content, even when protected by passwords or restricted access.
There was a bug in the filter share that caused a malfunction when sorting. However, it now works correctly when any sorting is applied from the table header.
Fixed an issue where long text overflowed in the summary section in External Share frame.
In the custom email tab, the “Authorize with Gmail/Outlook” text was not visible in dark mode. This issue has now been fixed.
There was a bug where public URLs with special characters (#
and ^
) in the "Name" field and password protection prevented access from Share Configuration. Now this issue has been fixed, user is redirected to the shared link.
The issue where users couldn’t access external shares with password-protected public links is now resolved.
Previously, protected public links didn’t work, but users can now open them without any problems.
Previously, when an external user accessed a shared link and made updates in Jira, such as changing a status or updating a description, the updates were either not sent or sent with a significant delay. This issue has now been resolved, and updates are sent promptly.
We fixed a vulnerability that allowed customer-level users to bypass password protection and access externally shared issues.
We’ve found a vulnerability that low-privileged users to change permissions, giving them unauthorized access to external shares. This has been fixed to prevent privilege escalation and ensure proper access control.
Reverse the color palete for dark theme
We need to reverse the color palette for dark theme.
In Jira color palette in light theme looks like:
Both checked buttons are signed as “dark green”. Atlassian reverse the color palette automatically when you switch a theme. So If you set a dark font on light background after switching to dark theme you’ll have a proper light font.
We need the same mechanism for External page.
This also causes a bug when editing the External share page
Also there was a mismatch in page theme editor theme when:
in global settings dark mode was disabled
users browser is set to darkmode
For testing:
Editor theme and inserted elements should behave similarly to editor in Jira,
for example:
dark text in light mode should turn light in dark mode (high contrast and visible)
Easiest way will be to compare editor behaviour/comments look between Jira and ESFJ.
Please check from both perspectives (both for light and dark mode):
check how comments posted from ESFJ look in Jira
check how comments posted from Jira look in ESFJ