Skip to end of banner
Go to start of banner

LDAP searches

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

The following solution was kindly provided by Stefano Gevinti.

Problem

When creating an issue, you want to first assign it to the manager of the current user, to enable prior decisions on category. However, the relationship between the current user and the manager is not declared in Jira (as a project admin, for instance), but in the LDAP.

Solution

create_postfunction.sil
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);
}

This post function should be the last in the call chain when creating an issue.

Now configure the LDAP.

This solution assumes that the Windows account name is the same one used to access Jira. This depends on the AD setup.

Table of Contents

  • No labels