Profiles

At the moment, the People Search & List Macro is only being sorted by the name, and there's no way to change that. For most applications that might be fine, but sometimes you want to sort by other criteria, for example by a date. There's two options here: a) a macro configuration option to determine which column the list should be sorted by, or b) the option for users, who are visiting the page, to sort the table themselves temporarily; on reload it would be back to default. If you vote for this, please share your opinion, which way you would prefer this - and also if you maybe have a third idea.

When using the People Search & List macro embedded on a page, sometimes it makes sense to limit the amount of people shown to a certain number, for example for layout reasons, so it fits better on the page. Someone commented on another ticket: "It would be great to be able to set the users per page manually, maybe with a default at 50 entries." So the idea is to give the macro an option where you can set the number of people shown per page when the result list is paginated.

The deprecated macro Custom User List has an expert mode where you can select users to list by using CQL statements. The new macro People Search & List doesn't offer this option. Therefore, some macros cannot be switched to the new version, they rely on using the CQL mode or expert mode. The idea now is to offer an expert mode for CQL queries in the new macro.

The existing macros "Custom User List" and "Custom User Search" are two of the oldest macros in the whole Linchpin Suite, and as such they are in dire need of a refresher. Also we have quite a few feature requests and bug reports regarding these two. After evaluating the possibilities we decided to not rework those two but leave them as they are. Instead, we want to introduce a fresh new macro that combines both user listing and user search and is based off of the much more recent implementation of the user directory. That way, we don't have to migrate all the old macros to a newer version, which very likely would cause all sorts of problems and possibly break existing uses. Instead, the existing pages with macros on them can stay functional while you test out the new macro. The first iteration will inherit the settings from the user directory (think columns of the list view, available filter options). In further iterations we plan to add more possibilities for the macro, so it might show different filter options or a reduced set of columns in the list view. For that, we'll rely heavily on your feedback - so if you are interested, keep an eye out for this and test the new macro when it's available :)

We use the profile macro on many pages in a sidebar layout. On smaller screens or when enlarging the left hand sidebar, the profile macro is not behaving responsive., which leads to incomplete display of the information, as the macro seemst to create an object with fixed width

When displaying Customized User Lists as easy-to-reference rosters, fields that are text based should wrap more naturally - at the start or end of words, or abiding by punctuation like commas. Otherwise, there are unnatural line breaks in several fields, including phone and email.

When I want to collect sensitive profile data in Linchpin User Profiles, I want to restrict access, so only specific people can see the users' information.

Due to the increased use of the home office, internal communication via the telephone system has been greatly reduced at our company. We use almost 100% Webex (formerly Webex Teams). On the Linchpin-vCards, the extension number is currently still displayed. This could be done by a dynamic link "webexteams: //im?email={cup.email} " as shown in the screenshot. Unfortunately the field cup.email is not available in LUP. In other linchpin macros like the Customized User List, however, it is available. Could you please provide the field in LUP so that a Webex chat could open directly out of the Linchpin-vCard?

"Date" should have the ability to change format (MM-yyyy for example)

For us, it is not possible at the moment to use the structural chart, because our structural data is maintained in AD / LDAP and delivered to Confluence as "text input". Linchpin only allowes to create the structural chart by field types "Select" and "Multiselect". So it would be nice to also allow the field type "Text input" to use data from AD. Double maintenance of data (AD and Confluence) is not practical for us.