• JSU-120 : JSU exit from portal user doesnt send notification to SU target
• JSU-111 : Email notification to SU target user

• JSU-120 : JSU exit from portal user doesnt send notification to SU target
• JSU-111 : Email notification to SU target user

• JSU-113 : Allow SU target group delegation, docs @ https://thepluginpeople.atlassian.net/wiki/spaces/JSU/overview

ERROR logs incorrectly shown for anon access

ERROR logs incorrectly shown for anon access

• whilst NOT vulnerable to the recent CVE, the log4j dependencies in SU were left arbitrarily defined by the platform, this update explicitly depends on 1.2.17-atlassian-13 for avoidance of doubt.

• whilst NOT vulnerable to the recent CVE, the log4j dependencies in SU were left arbitrarily defined by the platform, this update explicitly depends on 1.2.17-atlassian-13 for avoidance of doubt.

• JSU-91 - Atlassian CDN compatibility

• JSU-91 - Atlassian CDN compatibility

• JSU-89 - If JSD is not installed - SU to user returns 500 if user does not have application access

• JSU-89 - If JSD is not installed - SU to user returns 500 if user does not have application access

• JSU-87 - Make security exit time-out a configurable value
• JSU-88 - Use user keys for Auditing Purposes instead of user names/keys

• JSU-87 - Make security exit time-out a configurable value
• JSU-88 - Use user keys for Auditing Purposes instead of user names/keys

• JSU-86 - SU Dialog auto focused when opened

• JSU-86 - SU Dialog auto focused when opened

• JSU-84 - Configurable path to be redirected to when exiting SU

• JSU-84 - Configurable path to be redirected to when exiting SU

• JSU-82 - config screen css update

• JSU-82 : config screen css update

• SUPPORT-3320 : https://thepluginpeople.atlassian.net/wiki/spaces/JSU/overview#SUforJIRA-Centrallylogging?

For more on configuring a dedicated SU log, see the wiki

• JSU-64 - SU Exit redirects to previous users dashboard, does not refresh for new login
• JSU-73 - JSD Portal SU exit link does not take context path of JIRA url into account

• JSU-58 - Add SU exit button for Service Desk portal view

• JSU-58 - Add SU exit button for Service Desk portal view under profile menu
• JSU-64 - SU Exit redirects to previous users dashboard, does not refresh for new login
• JSU-73 - JSD Portal SU exit link does not take context path of JIRA url into account

• JSU-63, now catered for

• spaces in usernames broke SU in later Jira versions, back porting the fix in case tomcat is upgraded in 7.0-7.2.x series Jira.

• JSU-59 showed up some interesting issues with Swedish keyboards. Symbols should work, regardless of 'where' they are mapped on a keyboard, apparently not. Taking the path of least resistance, we change the keyboard shortcut to use just letters, which is the same as SU for Confluence: gu

• After several requests from different users, we've extended SU capability for sideways SU, so that 'admins' can SU to other 'admins' (but not sys-admins). As previously, 'sys-admins' can SU to all.

• In order to SU to a target user (and do anything) that user must have right to user Jira. This version identifies if Jira Service Desk is deployed, and in such cases, will 'allow' SU to that user, redirecting to the portal selection page. At this time its not possible to add an exit link in the JSD view.

• Seems something moved around, auiSelect2 needs to be specifically included in the context now.

The keyboard shortcut for this historically had a condition associated with it that asserted that the user was logged in. The condition is not invoked, and its presence seems to block the shortcut from working, so has been removed for now.

• fix an npe appearing in the log

• All fixed up for Jira 7.0 !

• user hover context SU links now have the XSRF token set
• name used for SU via user browser (JSU-36)
• logging shows name and key

• marketplace and vendor licensing need to be the same

• Until now the SU role was restricted to system admins which introduced a bit of a bottleneck, in order to make this capability more usable, it is now possible to include jira admins, and members of given group(s). This change can only be done as a system admin, and no user can SU to a system admin!
• Global keyboard shortcut g ^ has now had a condition added so only users with SU capability will see it listed in the ? popup.