Bugzilla 1291031 (q.v.) describes how the behavior of the SelectAll button, when viewing a filtered-list, violates the concept of "least user astonishment". For that BZ, the behavior was changed to make more sense - but only for the NewListTag-controlled pages. In the process of addressing that issue, uncovered an issue with the NewListTag: the existing support for filtering-on-parent and filtering-on-child was broken, was only taken advantage of on the DuplicateIP/IPv6/HostName/MACAddress pages, was only marginally 'working' there, and only as a result of some suboptimal code in a variety of places. The behavior on those pages interacts with filtering better now. Other behavior of those pages is no worse than it was before. However, the behavior of the NewListTag in the face of the Expandable interface and tree-structures, is fragile and occasionally user-surprising. This BZ is a placeholder to remind us to go back and clean the tag up. It needs to handle being able to filter-parent, filter-child, and their interactions with select-all, unselect-all, and filtering. See Expandable, DuplicateSystemsAction, ListFilterHelper, BaseSetHelper, and DataSetManipulator for a start on where we need to do more refactoring to restore sanity.
Spacewalk 2.8 (and older) has already reached it's End Of Life. Thank you for reporting this issue and we are sorry that we were not able to fix it before end of life. If you would still like to see this bug fixed and are able to reproduce it against current version of Spacewalk 2.9, you are encouraged change the 'version' and re-open it.