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 8 Next »

For the following steps you need Confluence Administrator permissions.

Configuration Overview

You can access the configuration via the menu item User Profile Settings > Profile Elements in the panel on the left side of the administration console (choose Cog icon > User Management at top right of the screen or use the keyboard shortcut: press 'g g' then type 'Profile Elements').

On this screen you have the Personal and Company sections as default. The full name and email are taken from JIRA itself, and cannot be edited. Below these elements, you’ll see the option to add a new element (“Add Element”). Once you click on this button, a new window will pop up where you’ll be able to create your own profile element.

There are a few options here:

  1. The Title – This is where you choose the name of the element.
  2. Help Text – You also have the option to add a help text. This will give a description of what this field means or a hint as to what’s expected in this field.
  3. Field Type Configuration – This allows you to choose the type of input the user has for this element. The options are a text field, a text area, a user field, single select (radio buttons), or multiple select (checkboxes). There’s also the option here to set up the element to synchronize with configured LDAP directories.
    • For the synchronization to work, you have to provide a mapping of LDAP attributes to standard or additional user profile elements. It is possible to relate more than one LDAP attribute to one user profile element. The mapping has to be provided at “Mapping for LDAP Attribute(s)” by using the following syntax:

      • Any LDAP attribute has to be given as %%LDAP_ATTRIBUTE%% (i.e. name of an LDAP attribute enclosed in two percent signs (%%)).

      • Multiple LDAP attributes with the same name are supported. If there are such attributes they will be mapped to the same profile field, separated by comma.

      • You can also specify static text (e.g. %%street%% %%number%% in %%city%%)

      • Use %%upp_delete_value%% as a placeholder to delete the data for previously synchronized profile element.

  4. Visibility – This enables the profile element to be seen on a user’s Hover Profile

Once you have some elements set up then you can rearrange the order on these elements with the up and down arrows on the Profile Elements main page. You can also edit each element or delete the elements you no longer want.

Please note, that the fields are only visible at the profile, if they contain any information. Otherwise they are hidden!

 


Back to Top

  • No labels