Bug 47698 - Sorting of containers and OUs is different in left pane and the "move" dialog
Sorting of containers and OUs is different in left pane and the "move" dialog
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - LDAP directory
UCS 4.3
Other Windows NT
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-08-30 09:34 CEST by Michael Grandjean
Modified: 2021-05-14 16:34 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 5: Will affect all installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.114
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Grandjean univentionstaff 2018-08-30 09:34:45 CEST
The left pane in the LDAP directory module is sorted alphanumerically, independetly of the container type (container or OU).
When moving an object, the sorting is different: first all containers are sorted alphanumerically, and then all OUs.

I don't know which one is better, but it should be consistent throughout all modules/features.
Comment 2 Florian Best univentionstaff 2019-03-17 00:36:02 CET
Probably they differ because I added sorting for the tree view so that IP addresses are sorted by their numeric value.
I think we could easily take that code to sort also the move dialog.
Comment 3 Ingo Steuwer univentionstaff 2021-05-14 15:43:22 CEST
This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.