| Button handy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Page Comparison
General
Content
Integrations
App links
| Button handy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
The following solution was kindly provided by Stefano Gevinti.
When creating an issue, you want to initially assign it to the current user's manager for review. However, Jira lacks a predefined manager role (for example, as a project admin). To address this, you need to access the Lightweight Directory Access Protocol (LDAP).
Enter the script provided below:
| Code Block | ||
|---|---|---|
| ||
string mgr = ldapUserAttr("manager", "(sAMAccountName=" + currentUser() + ")"); //get the current user's manager DN
string cnUser = substring(mgr, 0, indexOf(mgr,",")); //establish the cn, this is the manager user (that may depend on your setup)
string mgrUserName = ldapUserAttr("sAMAccountName", cnUser); //again, a lookup in the Active Directory to get the manager
//Note: these LDAP calls are automatically cached, so performance gets better if it is found in cache
if(userExists(mgrUserName)) { //make sure this is defined in JIRA
assignee = mgrUserName;
} else {
//fallback to project admin
assignee = projectPM(project);
} |
In this script, we used the preferred ldapUserAttr routine function but you can also use the deprecated ldapUserRecord routine function.
| Info |
|---|
When creating an issue, make sure that this post function is the final step in the call chain. |
Next, configure the LDAP.
| Note |
|---|
This solution assumes that the Windows account name matches the one used for accessing Jira. This depends on the Active Directory (AD) setup. |
Table of Contents
| Table of Contents |
|---|