Menu
▾
▴
#330 This bugtracker shows fixed/closed bugs
Originally created by: cumuluni... (code.google.com)@gmail.com
Originally owned by: cumuluni... (code.google.com)@gmail.com
What steps will reproduce the problem?
1. browse to https://code.google.com/p/flightgear-bugs/issues/list
2. wait for page to show up
What is the expected output? What do you see instead?
A list of open bugs only is expected but the entire list of bugs is shown
What FlightGear version (or GIT date)?
Does not depend on the FlightGear version (i use git latest git anyway)
This seems to have changed just recently?
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
Yes, our bug tracker has a bug. :-(
Workaround: Use "search" with option "-is:open".
Status: Accepted
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
... "is:open" that is.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: cumuluni... (code.google.com)@gmail.com
yep - works.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: gijsrooy
I filed a bug at Googlecode's bug-tracker ;)
https://code.google.com/p/support/issues/detail?id=5399
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
Thanks Gijs! Now everyone: vote for this Google bug (click the star at https://code.google.com/p/support/issues/detail?id=5399 ). May help to get a real (Google) person to actually look at it.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
We're probably not important enough for Google to care about us. And obviously their crappy database has an consistency issue. I "fixed" the problem by toggling all closed issues to status "temp" and then back to their original state (of course, making sure each issue returned to the exact state it had before).
"Bulk edit" is your friend here. Don't forget to disable "send email" when using bulk edit though, otherwise it triggers hundreds of email updates. And make sure you're not messing up everything with bulk edit - it's easy to destroy everything with it... ;-)
Status: Fixed