Apache OpenOffice (AOO) Bugzilla – Issue 16402
Need a sort key for IZ components
Last modified: 2021-05-27 19:28:19 UTC
For a user reporting an issue the start page http://projects.openoffice.org/project/www/issues/enter_bug.cgi is a mess. The components are listed in alphabetical order, consequently "wordprocessor", the component with the highest issue volume, is at the bottom, while many, many language components are listed at a more prominent place. With maybe hundreds more languages to come, this will become worse. We think we need a sort key for components, which enables us to define the order. This would still allow to generate the page automatically, but we'd have an influence on the sort order.
reassigning to support
Enhancement request PCN 20048 has been filed with the Project Management team. I will update this issue when they have updated the internal request or by 7/30/03. a possible workaround that you could try in the meantime is capitalizing the "W" in word processor, which I believe will make that component move to the top.
changing status whiteboard
Product Management replied to the internal issue. The use of Project Tracker in the futuer will take care of the enhancement request. Closing issue as resolved/fixed. 1) The workaround for this is to prepend the name of the component that you want earlier in the list with a special character, such as '*'. Capitalization will not work because components names are not case sensitive. 2) Project Tracker has the capability to explicitly order the attribute options which are the names that are available in a dropdown list. This way the administrator can set the order to be whatever they want.
reopening to mark it as resolved/later
The workaround for IZ seems to be fine. Michael might want to decide, whether we use it or not. Changing to resolved/later for verification with Project Tracker.
CollabNet Support is currently reviewing the issues under Resolved-Later. If the issues are fixed currently in any of the present CEE releases, then it will be marked as Resolved-Fixed. There might be a few issues which might not be in our future roadmap which might be closed as Wontfix unless it does not lie under any custom request.
This is currently available in Project Tracker