SU for JIRA
SU for JIRA
|Compatibility||JIRA 5 or newer|
What is SU?As a JIRA administrator you get users saying 'I cant do xyz', or you have conversations like 'you should see xyz' and the phone says 'no I cant'. You need to be your user to ensure clarity of instructions, and to spot/resolve other kinds of problems. Without giving passwords away, how do you do that? Well, you use this plugin. This plugin enables system administrators to become another user (to 'su' in Linux speak), enable setup, testing etc
- You can install this plugin via the universal plugin manager!
The Plugins 'configure' link lets you request an EVAL license. Follow the screenshots listed on the plugin page
1.5.x Dual Licensing
Versions above 1.5.x support dual licensing. This means that:
- Marketplace licenses (obtained via the Marketplace) can be installed directly
- Vendor licenses (obtained from The Plugin People or via the automated checkout process) can be installed via the Configure link (above). The license entry textbox is lower down, scroll down to locate.
@since JSU 1.5.4
A global keyboard shortcut is available for SU, to see available shortcuts press ?, to trigger the SU prompt, press the combination g + u, then you will get:
|User Prompt||User Selection||Ready to Submit|
@since JSU 1.5.5
Only system admins can configure who can SU, anyone with SU capability cannot SU to a user with system admin capability!
The SU keyboard shortcut will only be visible for people who have the SU capability
Appropriateness of SU is validated at the point of SU, so SU links will be shown for System admins etc.
The default behaviour is that System admins and JIRA admins are able to SU, access may also be granted to nominated groups (note: probably not a good idea to add jira-users into this!):
|Default Access||With Delegated Group Access|
The SU Exit for JIRA SU is accessed via the toolbar, as shown below:
With SU v1.8.3 (Jira 7.10.x), its now also possible to log out SU activity, to track common SU related actions (SU to userX, SU exit, history retention changes, manual purge etc).
Add the following to your JIRA_HOME/WEB-INF/classes/log4j.proprties file, it will then append high level actions to the give files, here, we create 'su.log' specifically to capture this info, but also send a copy to the console and filelog, remove as needed.
After enabling logging, in 1.8.5+ the following will be seen for SU and SU-Exit actions:
Manual Tweak required (Prior to V 1.4.4)
Modify the file /atlassian-jira/secure/admin/user/views/userbrowser.jsp to get a UI 'SU' link. Find the following (starting around line 182 in JIRA 5.2), the bold section is added to make the SU link visible.
<li><a id="su_link_<webwork:property value='name'/>" href="<ww:url page='JiraSU.jspa'><ww:param name="'name'" value='name' /></ww:url>">SU</A></li>
<li><a id="projectroles_link_<ww:property value="name"/>" href="<ww:url page="ViewUserProjectRoles!default.jspa"><ww:param name="'name'" value="name" /><ww:param name="'returnUrl'" value="'UserBrowser.jspa'" /></ww:url>"><ww:text name="'common.words.project.roles'"/></a></li>
The manual approach
Jira 3.x - 4.1.x Add the following beneath it:
Jira 4.4+ - 6.0
Once installed, as a system administrator, go to the User Browser, you will find a SU link in the Operations column. Clicking SU will reset who you are to the given user, and return you to the Dashboard.
Alternate usage (no install needed)
If your Jira isn't deployed to / you will need to update the url with the prefix:
Extend to allow 'exit' back to existing system admin user
Auto redirects to Dashboard on successful SU
bugfix, make work with /jira type context deployments, required interim 'click here' page to get to the Dashboard, couldn't figure out how to redirect straight there.