...
The following solution was kindly provided by Stefano Gevinti (thanks!)
| Info | ||
|---|---|---|
| ||
Power Scripts Scripts™ for Jira (server) Level: BASIC |
...
At creation time, you want to assign the issue first to the manager of the current user, to decide and categorize the issue. The problem is that the relationship between the current user and the manager is not declared in JIRA Jira (as a project admin, for instance), but in the LDAP.
Solution
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
string mgr = ldapUserRecord("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 = ldapUserRecord("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);
} |
...
| Note |
|---|
The above assumes that the windows account name is the same the user is using to access JIRAJira. This is really dependent on the AD setup. |