Javier, I've been playing around with trac_tickets.py for a bit and I've found an improvement that I would like to see implemented (maybe it's already there and I don't know?). After running the script I get a result like:
164054 [87] <-> [Auto-Generated] Bug Report - TypeError: unsupported operand type(s) for +: 'error' and 'str' 163628 [87] <-> [Auto-Generated] Bug Report - Exception: All request/response ids have to be integers. 163466 [72] <-> [Auto-Generated] Bug Report - UnicodeDecodeError: 'utf8' codec can't decode byte 0xff in position 0: invalid start byte 164146 [69] <-> [Auto-Generated] Bug Report - IndexError: list index out of range Which makes me think that 164054 is one of the bugs to be fixed. Then I go to Trac and search that ticket and it actually is already fixed. I then search for the "TypeError: unsupported operand type(s) for +: 'error' and 'str'" string and all of the search results are also fixed. In the code you seem to be searching for the tickets with status "new" ('status=new&component=automatic-bug-report...'). Does that work? Can we make it work so that the generated list is more useful? Also, when printing the tickets, can we print the ids that are grouped? I would like to have an output file that looks like: { '[Auto-Generated] Bug Report - TypeError: unsupported operand type(s) for +: 'error' and 'str'': [164054, ... , ..., ...] ... } With this information, when we fix one of these bugs we'll be able to close all the related bugs. What do you think? Would this help? Regards, -- Andrés Riancho Director of Web Security at Rapid7 LLC Founder at Bonsai Information Security Project Leader at w3af ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ W3af-develop mailing list W3af-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/w3af-develop