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'm not able to edit products that have empty description fields in IssueZilla. The products are not shown in http://www.netbeans.org/issues/editproducts.cgi and there doesn't seem to be any other way to access them via the IssueZilla admin interface. It is possible to file bugs against those modules though as they are displayed in http://www.netbeans.org/issues/enter_bug.cgi Examples of the modules with empty descriptions include: cpplite logger jasm vcscore
The problem is that someone forgot to enter description of product and SQL select in editproducts.cgi lines 207-212 (as in Bugzilla 2.10) cannot work with NULL fields. There are two possible solutions easier and (of course) more complicated: The easier way is to manualy update affected NULL fields using SQL "update" command (I recommend it). The more complicated way is to rewrite SQL select in editproducts.cgi lines 207-212 to handle also records with NULL fields. Another case is to fix database structure shown in checksetup.pl lines 665-666.
Done. Every product is in there with "default text". Please change when you get a chance. Added: cpplite itutor jasm logger nbbuild qa vcscore in tigris products table: insert into products values("vcscore","default text","",0,0); in issues product table: insert into products values("vcscore","default text","",0,0,10000,0,""); for future reference. This is what lead me to the answer ON products.product=issues.product line 225 in editcomponents.cgi. Rudolf was entirely right except the entries just didn't exist rather than existed with some NULL values in them.
Keri, since most of these projects were created via SourceCast admin interface, isn't it a SourceCast bug that the bug database's metadata was not fully updated after creating each project?
This is actually the Tigris infrastructure and at that point, Bug/Issuezilla wasn't as integrated as it is in Sourcecast -- so it has to be manual.
We recently moved out from Collabnet's infrastructure