On Monday 06 February 2006 07:39, you wrote: > hey > > I looked at your job for the bug report system, seems nice! > > So how does it work? What's the difference betwen bugs and wild bug > reports? > Basically I split it into two parts. There is bugs and bug reports. Bug reports are the thigs that are sent by the amsn client. Bugs are something we create with the website. To each bug we can assign bug reports that belong to it by pressing change by the bug parent thing in the bug report page. The window that pops up (it is JS, so if someone minds tell me) and you can pick a bug to assign it. If you want to create a new bug, press "New". The text box beside it is just a filter box thing. The default name is "New Bug", but you can change it later on. It's just somethign to quickly identify it. Then you can add regular expressions to match error text AND stack to find more bug reports that belong to this bug. Use the preview button to test your reg exp. Also you need to save it before doing the actual search. Also bugs are assigned a priority by a cron job that I run every hour or so. It basically searches all bugs that are marked as NONE and the one with the most reports is marked priority 100. All the other bug reports' priority is just their reports/most reports belonging to a bug * 100.
Another feature is that if a bug is marked as fixed and we recieve a report with a cvs version newer than the fix date (date when it was marked fixed), the bug gets reopened and an email is sent to the developer in charge of it. The developer field is basically email of the developer in charge of the bug. You have to type it in manually at the moment, but I plan to add a select box instead later on. Use "Nobody" if no one is in charge. Speaking of email, we can't send email from the webserver but we are allowed from the shell. So I have created a function called email($to,$subject,$body) in the sf.lib.php file that is used instead of the php mail() function. It just queries emails in a db that are later sent via a cron job. Since we are only allowed to send 100 emails per user, it might take a long time to send all if they are queried. It would be nice if more people had the script at different times to get rid of the load on my accound. The path to it is: /home/groups/a/am/amsn/htdocs/bin/sendemails Just don't run it at midnight, because that's when I'm doing it. Also the "from" is the user who sends it. Does someone know if it's possible to change this when using the "mail" command? Btw, wild bug reports that don't have a parent bug. Some things that I am aware of and should be fixed this weekend. -when filtering the table of bugs via a text box, the search query is not shown -not enough bugs per page, I'll switch it to the 50 per page we had before -some problems in the subject of emails -currently even the fixed bugs are shown in the table by default If you have any questions or suggestions, please reply. > Are all the bugs in the DB? > I removed the "fixed" bugs because of the change in the database layout. It was easier than making a script to convert it. If you want, I can put it back this weekend. I have a backup somewhere, exept I can't find it now :S. -- Karol Krizka
pgpsgp0GLCI47.pgp
Description: PGP signature
