The JELUS Enterprise LDAP User Sync plugin for Jira imports user attributes (including profile pictures) from Active Directory and LDAP Servers into properties of JIRA user profiles.
Support for profile pictures
JELUS allows you to manage your staff’s profile pictures within Jira in a way that is consistent with other enterprise-grade products such as Sharepoint and Exchange.
- Users no longer need to upload photos to Jira themselves, or have IT Support do it for them.
- JELUS ensures profile pictures in Jira matches those used across the organization.
- Profile pictures of new employees are automatically added to Jira after their Active Directory profile picture has been uploaded.
- Automatically resizes pictures to fit Jira’s profile picture size requirements.
- Easy to configure and test before activating the plugin.
Support for all Active Directory attributes
You decide which attributes are being synchronized with your Jira users. Synchronization can be triggered manually or you can benefit Benefit from the continuous automated synchronization using the JELUS scheduler or synchronize manually.
- Support for Supports multi-value attributes.
- View Preview all available attributes including a preview for a specific user before starting to synchronize.
- Support for multiple Active Directory and/or LDAP servers.
- Tightly integrated into Jira – you don’t have to configure any connection details
Display user attributes on the profile page
- Show user attributes in profiles depending on
- Directory and group the viewing user has
- Directory and attribute the viewed user is coming from
Show user attributes in custom fields
- Link valuable and helpful information such as contact information to Jira issues.
Show any user property from any user field in an issue
- Searching for these fields is currently experimental
10% discount for anyone providing translation to a new language - please check with us first if your language is already in translation
Simply install via UPM, then click the "Configure" Button.
Here you can configure each of your directory servers for synchronization.
For each server you can selecte the attributes,which will be written to the users profile.
A configuration in this terms is a per directory setting of attributes to synchronize and the choosen image attribute.
Re-Read Directories from JIRA
This will discard any directory information know to JELUS and read directories from JIRA. If a know directory is found again in JIRA it´s configuration will be kept - otherwise the configuration will be deleted. Found directories will also be checked for their available attributes.
Delete Sync Config
This will clear the configuration of all know directories, but will not remove the "known to JELUS" state of a directory.
- Configure the scheduler only via the provided "JELUS Scheduler" screen - NOT via the edit link in the service administration of JIRA
- Do NOT delete the scheduler in the service configuration of JIRA
- If you have a large userbase don`t choose an interval that is shorter than the manual sync takes to complete, future versions will correct this automatically
User Profiles & User Profile Configuration
Synchronized attributes from LDAP or Active Directory Servers can be used for various purposes. JELUS natively supports displaying all synchronized attributes in users' public profile.
Using the User Profile Configuration, JELUS gives you fine-grained control over the visibility of the synchronized attributes on users' public profile.
This simple 3-step process is depicted in the screenshot below:
- Create a new rule by clicking "Add Row".
- Select directory origin and group membership of users that you would like to grant the right to view synchronized attributes of other users.
- Select directory origin of users and their attributes that users selected in step 2 shall see.
Here is an example based on the screenshot above:
JIRA has been configured to synchronize with two user directories ("Active-Directory-Server" and "LDAP-Server").
The first row of the configuration states that
all users originate from either of the two directories AND are members of the "jira-users"-group
can view the attribute "telephoneNumber" on the public profile page of all users that originate from either of the directories.
The second row of the configuration states that
all users originate from either of the two directories AND are members of the "jira-administrators"-group
can view the attribute "employeeID" on the public profile page of all users that originate from either of the directories.
As all rules are additive (and assuming jira-administrators are also jira-users) the configuration above can be summarized as follows: Normal JIRA users can only see other users' phone number while administrators can see both, phone number and employee ID.
In a less restricted environment you may alternatively choose to show all attributes to all user. In this case, simply activate the Override check box.
Custom Field Configuration
Choose from a variety of fields:
Configure what attribute of which user you want to display
The following restrictions apply to JELUS licenses and their states
|License Type||within valid period||after expiry|
|none||without a license only 10 users / directory can be synchronized|
|evaluation||1000 users / directory||10 users / directory|
|paid||as per license count||10 users|
If you have a feature request or any trouble with JELUS please open an issue in our support system at auresso.atlassian.net. This will be the fastest way to get a response from us.
Enabling Detailed Logging
If you run into trouble with JELUS we can generally help you faster when you provide us with a detailed log file. JELUS will collect all necessary information when the logging level is set to debug.
There are two ways of archieving this.
- To enable debug-level logging, open the JELUS Administration Page. Append "?debug" to the URL, i.e. change the URL from
" " and press enter.
Select "Enable JELUS Debugging" in the JELUS configuration menu on the right
- OR open JIRA and select "System" -> "Logging and Profiling". Find the section "Default Loggers" and click on "Configure logging level for another package".
Use "net.auresso.jira.plugin.jelus" as the package name, select "Debug" as logging level and click "Add".
After activating debug-level logging use the JELUS feature again that you have trouble with. Afterwards please send us copy of your log file accompanied by a brief summary of what you did and what trouble you encountered.
Information about where to find the JIRA log file can be found at JIRA Documentation - Where are JIRA logs?.
If you encounter problems while saving the configuration you should also set the loglevel for "net.java.ao.sql" to Debug.
If your directory configuration was created before JIRA 5.0 in an osuser.xml file and migrated during the upgrade process, JELUS will not be able to work properly.
The following are known issues and will be fixed in upcoming versions
- Attributes deleted in the directory stay in JIRA
- After a manual change of an avatar in JIRA a new file is written during next sync
The following new features are on our roadmap and will be implemented in upcoming versions
- Make handling of multi-value attributes configurable
- Make the plugin cluster safe