This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I was searching for a module today in the SC Admin interface, at the URL above. I tried using the "filter this list" box at the bottom of the page - I entered the word "track" and hit the Filter button. I see a list of 4 modules and descriptions displayed - only 1 of which includes the word "track". A quick check of each of the 4 listed modules' home pages shows that the word "track" does appear in the HTML content of the page, so it looks like the Filter script is actually searching not just module names and descriptions, but index.html content as well. This might be useful elsewhere (though site search really ought to look after content searches), but it is definitely unexpected behaviour here.
Were your expectations based on some documentation?
updating whiteboard
No; the UI is very, very simple. My expectation was that "Filter this list" would filter the list.
Well, it does filter the list, just not in the simple way it was expected. I can put in a RFE on this as I agree with you, it should filter on the name of the list only (unless specified otherwise, which would probably be more along the lines of the search function).
There are 2 fields displayed in the list : project name and project description. A "filter" should "filter" whatever is displayed - from either field. For an example of a "filter this list" that works see the User list at http://www.netbeans.org/servlets/UserList. Here there are 4 fields displayed; filtering will list antyhing that matches in any of the 4 fields. This is a defect IMO, not an RFE.
It seems you are seeking consistency between the filters. If you filter in the user list, it filters on any and all items in the user's profile that would help to make it unique, e.g. username, real name, email, and organization. When you filter in the module name list, it also filters on any and all items in the module's profile that would help to make it unique, e.g. summary, description, and "use module home page" because it is in effect the module's description (as per the admin screen for the module: "Check this box to use your project's www/index.html file as the project's description. This is useful if you plan to have a complex home page.") Seeing as the two filters work in the same way and there is no documentation stating they should or do work in any other way, this would seem to be a matter of expectations not being met by the filter option. That would qualify as a request for an enhancement.
The difference between the 2 is that the User list filters on *visible* data. I have no idea of how many, or what, fields this module list really has. If they are not displayed, and I don't even know they exist, why would I want to filter based on them ? Or rather - how could I possibly find anyting I was looking for filtering on some unknown set of hidden fields containing data I can't even see !? A UI which allows you to filter a displayed list, but does so based on fields which are hidden from the current display (without any notification) is broken.
Hi Jack, I've just submitted this to the engineering team, citing the example of how "filter this list" works for the "Users" section as the behavior we'd like to see in the "Projects" section (and for all "filter this list" options throughout the site). In summary that "filter this list" should search the fields visible to us in that section. Thanks, Kristen
A target milestone has not yet been assigned to this issue as yet. Our plan is to update the issue as soon as we have more information from Product Management. The support team does check on these issues regularly. Please let us know if there are any additional considerations for this feature or concerns on the timeframe for the next update. Thanks, Jan
Change in our Update Plan: Our plan is to update this issue in 1 week. Please let us know if there are any additional thoughts on this issue or concerns about the timeframe for the next update. Jan
Update: We do not yet have an update from engineering on this issue. Action Plan: Request an update. Next update: Within 2 weeks. Thanks, Kristen
Update: Referencing additional internal tracking number, PCN 12961. Action Plan: There has been some research on this but we do not yet have a target milestone for the fix. Next Update: CollabNet support will check in on this issue again during the first week of December. Thanks, Kristen
update: here'is management decision - agreeing with Jack. 'The agreed to plan on this is to remove filtering on non-visible fields, which in this case is the long description. It is planned to be addressed in 2.5.1.' Action plan: verfy the planned milestone. Next update: in two weeks. Thank Jack for bearing with us on this.
update: upgrade to 2.5 will fix this action plan: we'll keep this issue open till upgrade confirms it.
update: the upgrade to truckee 1.x will solve this issue action plan:closing this issue and will confirm/verify after the upgrade.
Changing the milestone .
'Filter this list' now has two options 'Name' and 'Summary'. Projects can be filtered with any one of the above. Marking as verified
We recently moved out from Collabnet's infrastructure