Name | SU for Jira |
|---|---|
Author(s) | |
Homepage | |
Price | Commercial |
Compatibility | Jira 5 or newer |
Marketplace | |
Issues | https://thepluginpeople.atlassian.net/servicedesk/customer/portal/1/group/1/create/6 |
| Table of Contents |
|---|
What is SU?
| Excerpt |
|---|
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 |
Installation
You can install this plugin via the universal plugin manager!
License install
The Plugins 'configure' link lets you request an EVAL license. Follow the screenshots listed on the plugin page
...
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 |
|---|---|---|
 |  |  |
Controlling Access
@since JSU 1.5.5
...
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 |
|---|---|
 |  |
SU-Exit
The SU Exit for JIRA SU is accessed via the toolbar, as shown below:
...
| Code Block |
|---|
##==========================================
##
## SU logging
##
log4j.appender.SUFileLog=com.atlassian.jira.logging.JiraHomeAppender
log4j.appender.SUFileLog.File=su.log
log4j.appender.SUFileLog.MaxFileSize=20480KB
log4j.appender.SUFileLog.MaxBackupIndex=5
log4j.appender.SUFileLog.layout=org.apache.log4j.PatternLayout
log4j.appender.SUFileLog.layout.ConversionPattern=%d %t %p [%c{4}] %m%n
log4j.appender.SUFileLog.Threshold=INFO
#
# add entries for all SU packages
#
log4j.logger.com.javahollic.jira.jsu=INFO, console, filelog, SUFileLog
log4j.additivity.com.javahollic.jira.jsu=false |
Legacy Logging
| Status | ||||
|---|---|---|---|---|
|
| Code Block |
|---|
##==========================================
##
## SU logging
##
log4j.appender.SUFileLog=com.atlassian.jira.logging.JiraHomeAppender
log4j.appender.SUFileLog.File=su.log
log4j.appender.SUFileLog.MaxFileSize=20480KB
log4j.appender.SUFileLog.MaxBackupIndex=5
log4j.appender.SUFileLog.layout=org.apache.log4j.PatternLayout
log4j.appender.SUFileLog.layout.ConversionPattern=%d %t %p [%c{4}] %m%n
log4j.appender.SUFileLog.Threshold=INFO
#
# add entries for all SU packages
#
log4j.logger.com.javahollic.jira.jsu=INFO, console, filelog, SUFileLog
log4j.logger.com.javahollic.jira.web.action=DEBUG, console, filelog, SUFileLog
log4j.additivity.com.javahollic.jira.jsu=false |
Centrally logging?
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.
Code Block <td data-cell-type="operations"> <ul class="operations-list">.. <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>... </ul> </td>
The manual approach
Jira 3.x - 4.1.x Add the following beneath it:
...