#219 sort by uid instead of cn in dirbrowser
Closed: wontfix 4 years ago by mreynolds. Opened 12 years ago by rmeggins.


A customer requests that the Directory Browser sort with uid as first key, or
make sort order configurable.  The reason is that the label it displays for
entries is always the RDN; they have entries with uid as the RDN, but the
Directory Browser uses cn as first sort key, so even though the entries can be
considered to be sorted, the list looks wrong since the uid is displayed.

I think it makes some sense to use uid as the first sort key since the
New->Person template uses uid as RDN.

batch update moving tickets to future

set default ticket origin to Community

Added initial screened field value.

Metadata Update from @rmeggins:
- Issue set to the milestone: 389-admin,console FUTURE

7 years ago

Admin server/Console is deprecated, closing ticket...

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None (was: Needs Review)
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 years ago

Metadata Update from @spichugi:
- Issue set to the milestone: FUTURE (was: 389-admin,console FUTURE)

3 years ago

Metadata Update from @spichugi:
- Issue set to the milestone: Legacy (was: FUTURE)

3 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/219

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Log in to comment on this ticket.