Working in a big company, it can be hard to find a particular person – or even to figure out who to reach out for in the first place. In such companies, user data is usually stored in Active Directory (or on some other kind of LDAP server) and is managed by a dedicated admin. But when you also use Atlassian Jira for managing the projects that you work on, you can synchronise its internal database with Active Directory and put the two powers together to have more actual information about the users at hand. This will make your team’s work much easier, as well as the admin’s work.
Jira provides built-in connectors for the most popular LDAP servers, such as Microsoft Active Directory, Apache Directory Server, Fedora Directory Server and a bunch of others. After the connection has been established, the information on users is cached and stored in the internal Jira’s database. Every time a user logs in, the user’s data is updated from the corresponding fields on the LDAP. By default, this includes username, display name, email address and group memberships. But LDAP servers often store other contact information as well – phone numbers, departments, managers’ names or some custom attributes. Is there any way we could use it in our work?
We’re not able to do it natively, but we’ll find apps which enable us displaying Active Directory attributes in Jira. One of these apps is Active Directory Attributes Sync, which we can use to show any available information form Active Directory in user profiles, hover dialogues, in a custom field at the issue view, and even on the Customer Portal. We can set up how often we want to synchronise the displayed data, thus making sure that it’s always up-to-date.
Firstly, we should go to the app’s configuration and select the fields that we want to be synchronised with the database. Besides the default user attributes, we can also add there any custom attribute available on the server. We need to be careful when providing the fields’ names from AD – they should match perfectly to synchronise. The fields in Jira that will display the data are custom, so it’s up to us how we name them. Then, choose where we want to show these fields: on the app’s configuration screen, we can set up every attribute separately to display at the user’s public profile and the hover dialogue. Here is the resulting view of such a setup:
The customization of Active Directory user attributes for issue view and Customer Portal looks slightly different, because we need to create a dedicated custom field and add it to the appropriate screens. To do so, we need to:
Setting up Active Directory user attributes in Jira Service Desk with Active Directory Attributes Sync
We’ll find the AD user attributes in the right column of the request on the Customer Portal, as well as in the Details section on the issue view. This way both our teammates and customers will know how they can reach the assignee outside Jira Service Desk. And besides just displaying the contact information, we can manage it, as well as the Active Directory accounts right inside Jira with the help of Active Directory Attributes Sync.
If you’d like to learn more about Active Directory Attribute Sync, take a free 30-day trial from the Atlassian Marketplace, or watch this video tutorial to know 10 best ways to make it work for your company. You can also book a live demo via Calendly, if you’d like to see the app in action, or read more on the subject:
Also published on Deviniti blog.
Dzmitry Hryb [Deviniti]
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs